"Thorsten Froehlich" <tho### [at] trfde> wrote in message
news:3dd631b5$1@news.povray.org...
> The original poster (Andrew) assumed that he would have to stop POV-Ray
> manually, Warp assumed POV-Ray instances would communicate in some way, and
> there is absolutely no way to guess what someone else is assuming if it is
> either extremely hard to use (Andrew) or requires some fairly complex
> network interaction if done optimally (Warp).  I am unable to do
> mindreading, and neither assumption is logical, feasible or usable.

Why on earth is my suggestion "extremely hard to use"? IMO it's totally logical, and
useable.
For me (someone who often struggles with the POV SDL), it would be hard (or just a
major
hassle and timewaste) to have to re-write a scene to make it render backwards (I don't
even
know how I would go about doing that).

I admit to not having thought about problems that may arise when running two or more
instances
of POV-Ray on the one machine, and having one or more rendering backwards - with the
Windows
version, couldn't one just disable the feature if  Keep Single Instance was unchecked?
I don't
know if something similar is possible on other OS's.

My suggestion / request was for a simple command-line switch that would let POV-Ray
render
from the last frame to the first (when POV-Ray is running on seperate machines!). It
didn't
strike me that this would be a difficult thing to do (but then, what do I know? ;-)).
I never
intended a discussion on networking etc.

I have made (what I consider to be very useful) suggestions in the past, but which
have not
been implemented (I won't say 'ignored', 'cause I don't know) such as having Pause
Render
available by right-clicking on the tray icon. I always assume that there are good
reasons why
these things aren't implemented, and never take it personally. This is just another of
those
things, and is not a problem.

All the best,

Andy Cocker

Post a reply to this message