> the thought did occur - hey, Gilles, Mark, why do you need to hide it? What
> happens if you don't?

I am using the Unix version. It has only two visible outputs.
One is the preview window which I disable for these purposes.
The other is a very verbose stream that goes to stdout and
hence appears in my shell. I guess I COULD hide that by
piping it to /dev/null but I have not bothered so far: It is
easy enough to ignore the shell output because at that time I
work with a different shell.

The use in question is a run of make, some script, or some other
program that produces MANY images using povray. If, as the
license suggests and the Unix version does not implement, it is
required to let the user really know that povray is running by
presenting some popup each time povray is called, I would not be
able to work in the meantime. Every two minutes or so another
popup would bother me, just like ad-infested websites do.

It is acceptable, I think, to have a popup of that kind if you
are working on ONE scene that takes long to render and you give
it a try only every two hours. But it is not acceptable if, as I
do, you use povray as the backend of some program.

Post a reply to this message