20020829: gempak postscript creation

David,

You must run gpend when you are finished creating your postscript file
(same as with gif and other drivers).

Until you run gpend, the postscript file can still be appended to
by other programs for overlays etc.

When you run gpend, it will add the grestore and showpage trailers.
Until them you are seeing the buffer flushing out parts of the post script
drawing commands as the buffer is full. With the gif driver, you won't
see any output file until running gpend since only then can the screen image be
created. With postscript, since each drawing stoke isused, the output file will 
exist
as soon as there is enough information in the buffer to be pushed out to disk.

Steve Chiswell
Unidata User Support



>From: David Fitzgerald <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200208292007.g7TK7vZ29046

>This message is in MIME format. Since your mail reader does not understand
>this format, some or all of this message may not be legible.
>
>------_=_NextPart_000_01C24F97.BFC9BAC0
>Content-Type: text/plain;
>       charset="iso-8859-1"
>
>Hi guys,
>
>We found a weird problem in sfmap (and probably others) when we
>set the device to PS.
>
>The postscript output file is created but is not complete.  Its
>almost as if the file creation stopped in the middle.
>
>I've attached a sample of the type of postscript file we are seeing.
>
>Can you give me some guidance on where to look for the problem?
>
>Thanks!
>
>Dave
>