Re: PM3D postscript microgaps vanished from 4.0 to 4.1...

[Hans-Bernhard B. <br...@ph...>]

On Thu, 15 Jul 2004, Petr Mikulik wrote:

> > a newsgroup poster just found out a problem with (at least) post.trm pm3d
> > output exposed by turning on antialiasing (type 'a' in gv or ghostview)
> > --- there's a Moir'e pattern of very thin (single-pixel) white lines
> > exposed at the border between neighboring rectangles of pm3d plots.
> 
> It was always like that -- happens if you set option "Graphics Alpha" to 4
> bits (in gsview, I don't know how to change it in gv).

That just means it was always buggy, then.  (and yes, turning 
on 'Antialising' in gv does exactly that --- it sets the device to 
x11alpha, which in turn is described like this:

This is the x11 device, but with antialiasing. It is equivalent to
invoking the x11 device with the options -dGraphicsAlphaBits=4
-dTextAlphaBits=4 -dMaxBitmap=50000000


> That's the new postscript code in 4.1?! I don't like it, sorry! It breaks
> compatibility with all those pm3dConvert* scripts, and puts a lot of
> "useless characters" into maps. I'm against this change!

I'll leave it to you and Ethan to sort this out among yourselves...

> I.e., "pm3d map" should not be interfered by PolyFill. Why did this happen?

The goal would have been to get 'with filledcurves' to support pattern
filling.  Why it also triggers changes for plain 'with pm3d' plots
I don't know.

-- 
Hans-Bernhard Broeker (br...@ph...)
Even if all the snow were burnt, ashes would remain.