In article <40651522$1@news.povray.org>, dne### [at] sanrrcom says...
> Patrick Elliott wrote:
> > I think you can, but it is impractical, since I believe it will write out 
> > the file, but also attempt to continue to render. Any solution that gets 
> > around this requires using the confusing plugin architecture to interrupt 
> > it before it actually start the render I think. 
> 
> Nah. You wait until the file it writes out stops changing, then you kill 
> the process. Or you let the server trace the first scanline. (Of course, 
> all this assumes that radiosity works when you distribute the image to 
> start with.)
> 
> For that matter, if you wanted to kludge it hard enough, you could do 
> the whole thing with just +C, by shipping faked part-finished images to 
> all the machines, starting them up, watching how many scanlines of the 
> files had been changed, and killing off the render when it got thru as 
> many lines as you wanted. You don't even need the +S/+E, technically.
> 
I have a personally hatred of kludges. They rarely work as well as a 
correct solution. To many moving parts (or processes in this case). lol 
Just because a thing can be done, does not mean it shouldn't be done 
right.

-- 
void main () {

    call functional_code()
  else
    call crash_windows();
}

Post a reply to this message