[GRASS5] PNG driver problem

[Hamish]

> > Do you know if there will be a future command for 
> > writing the PNG file so we can call it when we please?
> 
> That would involve extending the driver protocol, which I don't
> particularly want to do without a compelling reason.
> 
> I wouldn't consider this to be a compelling reason unless there's
> empirical evidence to show that writing the PNG/PPM file takes a
> significant amount of time relative to the other parts of the process.
> 
> > As a temporary work around, what do you think of a GRASS script
> > which executes a sequence of commands before exiting? Would the PNG
> > driver consider that as a single operation and write once, or will
> > it write everything automatically?
> 
> The file is written when a client (d.* program) disconnects.


what about using the Unix 'sync' command in the script when
GRASS_PNG_AUTO_WRITE=TRUE

?


Hamish