Re: Bug #1503114

[Daniel J S. <dan...@ie...>]

Hans-Bernhard Br=F6ker wrote:
> Daniel J Sebald wrote:
>=20
>> That is what I'm suggesting.  Below is an example of something for the=
=20
>> longest time I couldn't understand, i.e., why the yrang here is as it=20
>> is.  The y range could be forced to make it look better.
>=20
>=20
> Well, guess what: I just tried that example myself (OpenWatcom build fo=
r=20
> MS Windows, terminal windows), and got nothing like what you got in
> that PNG.  The yrange I got was [1:2], exactly as expected.
>=20
>> What is happening there?
>=20
>=20
> Whatever it is --- it's not happening here where I sit and type this ;-=
)

Good grief.  I just looked at the "reference", i.e.,

http://gnuplot.sourceforge.net/demo_4.1/pm3d.html

and that too looks correct.  (However, the 3D example right after those, =
with the title "pm3d explicit mode" doesn't have the range [-3:3] [-3:3] =
as I think it should.)

I've seen this on my machine for at least a year, if not years!


> You'll have to debug that yourself, I think.

Sounds CPU dependent; I'll locate an oscilloscope.

Dan