Re: /YNOZERO [message #42765 is a reply to message #42702] |
Fri, 25 February 2005 01:13   |
Paolo Grigis
Messages: 171 Registered: December 2003
|
Senior Member |
|
|
Mr. No Address wrote:
> David Fanning wrote:
>
>> Mr. No Address writes:
>>
>>
>>> I'm using !P.MULTI = [0,2,2] though and each new instance of Plot
>>> creates a plot in the next panel. Of course, there is probably a way
>>> to prevent that...
>>
>>
>>
>> I'd try NOERASE for starters. :-)
>
>
> OK, I'm going to plead ignorance and stick with what I've done that
> accomplishes essentially what I want. Setting the range to MIN,MAX
> values as determined by the MIN MAX functions. I did try NOERASE but
> with initially unexpected results, but reasonable once considered.
> Everytime I look at the description of AXIS though, I keep getting lured
> in by the availability of /YNOZERO and the description "The new scale is
> saved for use by subsequent overplots if the SAVE keyword parameter is
> set." I see it says "new scale is saved," but /YNOZERO has as part of
> the description "...and no explicit minimum Y value is specified." So
> it _should_ be able to "see" into the future!
Then maybe the flaw is in the manuals here...
The behaviour of axis seems to be like this:
- if yrange is explicitely given, use that yrange
(/ynozero not relevant)
- if yrange is not given, than take !y.crange as yrange
(/ynozero not relevant)
- if !y.crange is undefined (that is, equal [0,0], I guess)
than use [0,1] as yrange (/ynozero again unrelevant)
(example:
IDL> plot,[10,13,12,11],yrange=[10,20]
IDL> axis,1,0,/yaxis,yrange=[9,15]
IDL> axis,1.25,0,/yaxis
IDL> !y.crange=[0,0]
IDL> axis,1.5,0,/yaxis
)
So it seems to me that /ynozero does not really affects the
behavior of AXIS, and maybe its documentation should be removed
from the manuals...
Cheers,
Paolo
>
> Anyway, I think for me this isn't worth pursuing further as my
> "solution" is perfectly adequate.
>
> Gary
>
|
|
|