comp.lang.idl-pvwave archive: archive » Re: Function graphics /OVERPLOT redefines axis limits after plot with /NODATA

Home » Public Forums » archive » Re: Function graphics /OVERPLOT redefines axis limits after plot with /NODATA

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Function graphics /OVERPLOT redefines axis limits after plot with /NODATA [message #80706]

Thu, 05 July 2012 17:40

wlandsman
Messages: 743
Registered: June 2000

Senior Member

On Thursday, July 5, 2012 5:11:21 PM UTC-4, nerdzoo wrote:
> On 7/3/12 9:25 PM, wlandsman wrote:

>> Yes, it is fixed in V8.2. In V8.1 you can use the following workaround
>>
>
> I don't think it is fixed. I observe the same weirdness in this system:
>
Yeah, I withdraw my statement that the /overplot problem is fixed in V8.2. I must have neglected the /nodata keyword in my quick test. --Wayne

Report message to a moderator

[Message index]

		Re: Function graphics /OVERPLOT redefines axis limits after plot with /NODATA By: wlandsman on Thu, 05 July 2012 17:40
		Re: Function graphics /OVERPLOT redefines axis limits after plot with /NODATA By: nerdzoo on Thu, 05 July 2012 14:11
		Re: Function graphics /OVERPLOT redefines axis limits after plot with /NODATA By: Paul Van Delst[1] on Thu, 05 July 2012 14:04
		Re: Function graphics /OVERPLOT redefines axis limits after plot with /NODATA By: wlandsman on Tue, 03 July 2012 19:25

Previous Topic:	Re: Function graphics equivalent of !X.OMARGIN?
Next Topic:	(more) Efficient way to generate an array whose elements are the distance from the center

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Oct 08 15:59:59 PDT 2025

Total time taken to generate the page: 0.00419 seconds