comp.lang.idl-pvwave archive: archive » Function graphics axis range

Home » Public Forums » archive » Function graphics axis range - how to get it consistently?

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

Re: Function graphics axis range - how to get it consistently? [message #87872 is a reply to message #87870]

Fri, 28 February 2014 11:00

chris_torrence@NOSPAM is currently offline

chris_torrence@NOSPAM
Messages: 528
Registered: March 2007

Senior Member

On Friday, February 28, 2014 11:34:05 AM UTC-7, Paul van Delst wrote:
> Oh my God, check this out:
>
>
>
> I added print statements before and after the various plot/text calls
>
> like so:
>
>
>
> print, tp[0].YRANGE
>
> c = PLOT( [date_time[idx[i]],date_time[idx[i]]], tp[0].YRANGE, $
>
> XTICKFORMAT='LABEL_DATE', $
>
> LINESTYLE='dashed', $
>
> /OVERPLOT, $
>
> BUFFER=buffer )
>
> print, tp[0].YRANGE
>
> t = TEXT( date_time[idx[i]], (tp[0].YRANGE)[1], $
>
> comment[idx[i]], $
>
> FONT_SIZE=7, $
>
> /DATA, $
>
> TARGET=tp[0], $
>
> ALIGNMENT=0.5, $
>
> VERTICAL_ALIGNMENT=1.0 )
>
> print, tp[0].YRANGE
>
>
>
>
>
> This is the output:
>
>
>
> 0.0000000 350.00000
>
> 0.0000000 400.00000
>
> 0.0000000 400.00000
>
>
>
> So the PLOT() command uses the "busted" YRANGE property value, but doing
>
> so "fixes" it.
>
>
>
> WTF?
>
>
>
> I give up.
>
>
>
> On 02/28/14 13:18, David Fanning wrote:
>
>> Paul van Delst writes:
>
>>
>
>>> To paraphrase Inigo Montoya, regarding the property YRANGE:
>
>>> "You keep using that word. I do not think it means what you think it means."
>
>>
>
>> It has been one of those days. (Well, honestly, it has been one of those
>
>> weeks.) I finally got a chance to take a shower a few minutes ago and I
>
>> was thinking as the hot water splashed over me, that as long as I was
>
>> asking philosophical questions that remain unanswered, here is another.
>
>> When you say:
>
>>
>
>> "For the record, I use FG pretty much exclusively.
>
>> I think they're great."
>
>>
>
>> Do you mean great from an "idea" perspective? Or do you mean great from
>
>> a "practical" perspective? Because I find them to be a long, long way
>
>> from "great". Sometimes I don't understand what reality I live in. Blame
>
>> the ganja wafting over me from all quarters now, I guess. :-)
>
>
>
> Albert Einstein -- 'In theory, theory and practice are the same. In
>
> practice, they are not.'
>
>
>
> Grr argghh!

Hi Paul,

I don't think you need to use a PLOT to do your dashed line. When you do an overplot, it's going to try to update the range to fit your new plot line. Instead, you could just use a polyline:

IDL> p = plot(/test, xrange=[0,250], yrange=[-1,2])
IDL> p1 = polyline([200,200],p.yrange, /data, linestyle='dashed')

Hope this helps.
Cheers,
Chris

Report message to a moderator

[Message index]

		Function graphics axis range - how to get it consistently? By: Paul Van Delst[1] on Fri, 28 February 2014 08:37
		Re: Function graphics axis range - how to get it consistently? By: Matthew Argall on Fri, 28 February 2014 08:50
		Re: Function graphics axis range - how to get it consistently? By: David Fanning on Fri, 28 February 2014 09:15
		Re: Function graphics axis range - how to get it consistently? By: Paul Van Delst[1] on Fri, 28 February 2014 10:06
		Re: Function graphics axis range - how to get it consistently? By: David Fanning on Fri, 28 February 2014 10:18
		Re: Function graphics axis range - how to get it consistently? By: Paul Van Delst[1] on Fri, 28 February 2014 10:34
		Re: Function graphics axis range - how to get it consistently? By: chris_torrence@NOSPAM on Fri, 28 February 2014 11:00

Previous Topic:	Orientation of Contour Labels
Next Topic:	Mavericks: NG plots start out black

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Thu Oct 09 07:22:43 PDT 2025

Total time taken to generate the page: 0.24055 seconds