Re: postscript terminal bug?

[Ethan M. <merritt@u.washington.edu>]

On Friday 09 June 2006 12:36 pm, Daniel J Sebald wrote:
>
> Here's the problem.  I'm paging through the output of 'pm3d.dem', call 
> it 'pm3d.ps', for the postscript terminal.  If I linearly step from 
> page 1 through page 41 the palette is correct.  However, if I jump
> about, the palette is not correct.

Got it.  OK, so the optimization cannot work for PostScript.
We'll have to revert the special-case PostScript code.

The bug in gsave/grestore that this code reveals may still be there,
but it probably won't bite anyone.  The mismatch is revealed because
the gsave is triggered by code that was made conditional, whereas the
corresponding grestore (wherever it is) is unconditional.

> What does PDF do?

PostScript is the odd man out because post.trm is the only driver
that pushes the task of assigning palette colors into the output
file itself.  For all other terminals, including PDF, the
core code keeps track of what colors to use in rendering
the current plot. 


-- 
Ethan A Merritt
Biomolecular Structure Center
University of Washington, Seattle WA