|
From: Ethan M. <merritt@u.washington.edu> - 2007-06-28 19:57:17
|
On Thursday 28 June 2007 00:22, Hans-Bernhard Br=F6ker wrote: > > Well, it feels like I've preached against the way 'map' was implemented= since > > day one. Nobody listened. >=20 > I coded the "set view map", I've listened to your comments, but I had fea= r=20 > to hit your axes module. So the status is as is. >=20 > > it took years to sort out that mess >=20 > yes; and I was glad when it finally worked for all cases I was not around at that time, and don't know the history or intent of the axis.range_is_reverted flag. =20 Could someone enlighten me on how this is supposed to work? The current behaviour seems inconsistent, so I am having trouble trying to make the "refresh" code to behave equivalently. =46or example, the following pair of commands produce a mirror pair of plots: set yrange [-300:300] noreverse; plot 'silver.dat' set yrange [-300:300] reverse; plot 'silver.dat' But the following pair produce identical plots: set yrange [300:-300] noreverse; plot 'silver.dat' set yrange [300:-300] reverse; plot 'silver.dat' So I am confused. =20 Does "reverse" mean "interchange the requested min/max"? Or does it mean "force the min to be greater than the max"? The latter appears to be true, but in this case the flag seems very much mis-named. =46urthermore, some plot/replot/zoom operations appear to clear this flag; others do not. So I cannot count on the current state of the flag being the same as it was originally. This again poses a problem for "refresh". And that's before I even get to splot_map... =2D-=20 Ethan A Merritt |