| Re: Rant about axis range defaults using overplot in object graphics [message #91661 is a reply to message #91658] |
Tue, 11 August 2015 07:48   |
![Paul Van Delst[1] is currently offline](theme/default/images/xoffline.png.pagespeed.ic.XRkd1fkXye.png "Paul Van Delst[1] is currently offline")
Paul Van Delst[1]
Messages: 1157
Registered: April 2002
|
Senior Member |
|
|
On 08/11/15 05:57, alx wrote:
> Le mardi 11 août 2015 01:33:41 UTC+2, laura...@gmail.com a écrit :
>> I know you Exelis folks are lurking out there, so why, oh, why,
>> haveyou used the default of changing the axis ranges to match the new data
>> when doing an overplot in object graphics? When I overplot data, in most
>> cases I want to just overplot the new data on top of the original data
>> (oddly enough). I think most of the time, people would like to keep the
>> same axes unless they specifically ask to change them. It is a pain in
>> the a** to keep restoring the axis ranges every time I add a new set of
>> data.
>>
>> (Note: If there is a way to override this default aside from
>> constantly specifying the original axis ranges as separate properties
>> every time I do an overplot, please let me know. I can't find any
>> reference to this in the Exelis documentation or on this website.)
>
> A simple way to overplot without changing axes:
> plot = plot(...)
> overplot = plot(/OVER, ..., XRANGE=plot.XRANGE, YRANGE=plot.YRANGE)
> You might even substitute /CURRENT to /OVER keyword in this case.
Yes, this is what I do when I want to retain the original plot range.
Sometimes I also find the range adjustment behaviour annoying.
But sometimes it's quite handy to have the automatic adjustment of plot
range to include all of the data in the overplots. Several times I've
discovered weird things in my data because the overplot adjusted in
function graphics (that I would've missed - initially at least - if I
was using direct graphics).
So, I'm happy to use the method alx detailed to prevent the
auto-plot-range-adjustment because I know sometimes it is useful.
I'm not sure if I can say this without sounding condescending to the OP
(I don't mean to be), but this was one of those times with IDL function
graphics where I simply weighed my perception anchor and dropped it
someplace else.
cheers,
paulv
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
