Program ended abnormally on 11/03/2004 09:59, Due to a catastrophic Chris Cason 
error:
> "Gilles Tran" <gitran_nospam_@wanadoo.fr> wrote in message
news:401cfdda$1@news.povray.org...
> 

>>news:4o4### [at] tritonimagicode...
>>
>>>Gilles Tran wrote:
>>>
>>>>Using the +C +F options (resuming and file output) when the file doesn't
>>>>exist yet causes the parsing to abort with an error message saying
>>
>>"Continue
>>
>>>>Trace Error: Error opening BMP image". +C alone (without file output)
>>>>doesn't cause the problem.
>>>
>>>Does this only happen with sys (bmp) file format or also with others?
>>
>>Only with the sys format (+F or +FS on Windows).
> 
> 
> I'm just fixing this now.
> 
> What would you prefer it do in the case where the file exists, but is (a) corrupt,
(b) of the wrong format (e.g. bit-depth), or (c)
> of the wrong resolution.
> 

You could warn the user and offer and interactive choice to:
(a) start from scratch, overwriting the file.
(b) start from scratch, renaming the previous file.
(c) continue using the original file's resolution and color depth.
(d) abort the render.

Or maybe, if and interactive choice is not a good idea, have these behaviours be 
part of an .ini setting.


-- 
/*Francois Labreque*/#local a=x+y;#local b=x+a;#local c=a+b;#macro P(F//
/*    flabreque    */L)polygon{5,F,F+z,L+z,L,F pigment{rgb 9}}#end union
/*        @        */{P(0,a)P(a,b)P(b,c)P(2*a,2*b)P(2*b,b+c)P(b+c,<2,3>)
/*   videotron.ca  */}camera{orthographic location<6,1.25,-6>look_at a }

Post a reply to this message