On 8/16/21 8:08 AM, jr wrote:
> phew.. I'm not sure what event POV-Ray would want to pass to the application,
> could you .. flesh this out a little, please? but there'd be other mechanisms,
> pipes, dbus?
First, thanks for the detailed response. I'll add it to my notes for the
next attempt. And on seeing your posted example, it does ring a bell...
Sorry if I did miss it - or forget I saw it posted.
Re: dbus, pipes. Your guessing my aims correctly.
There are crude ways to call povray in a loop today - adjusting say
spline control points. Such an approach which would be made much cleaner
with some sort of window id / into functionality as you've suggested.
Such an approach if, working with Tk frame widows, opens up Python and
Tcl as the scripting mechanism for "modeling/simple POV-Ray created
However, I'd like something a step beyond this coupled with rtr - which
in my minds eye at the moment - requires a couple of os level tasks be
talking to each other(1) continuously - or to, perhaps, be aware of X11
events in a shared way.
I'm ignorant of too much at the moment to know what I really want.
There are all the widget packages too - Qt, etc. With povr, I'm aiming
at more of a small utility niche with little or no overhead - something
'easy'. Pipe dream I expect, but a push here and a push there and maybe
some path to such a thing opens up....
(1) - POV-Ray has Thorsten's povms which has some facilities for such
communication. While I've learned tiny bit about that code of late, I'm
a long, long way from being able to swing that code around as a useful
hammer inside POV-Ray - let alone extend it.
Post a reply to this message