| Re: iplot, /xlog [message #49874] |
Fri, 18 August 2006 19:03 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
David Fanning writes:
> Kenneth P. Bowman writes:
>
>> A more basic problem is that PLOT uses XLOG and YLOG, while iPlot uses
>> X_LOG and Y_LOG. Not the best human factors engineering.
>>
>> Keywords may be slightly more consistent in the iTools, but explain
>> NO_SAVEPROMPT. Why isn't that NO_SAVE_PROMPT?
>
> I didn't say I could explain it. Only that I choose
> to see it as part of IDL's charm. How else could you
> remain sane?
Sometimes these keyword names, by the way, are chosen
to *expressly* avoid problems with keyword inheritance
chains. I wouldn't be a bit surprised to learn that
something like this turned XLOG into X_LOG.
I'd look into it, but I am still recovering from
something I picked up in Africa and I don't need
any more troubles. :-)
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. (Opata Indian saying, meaning "Perhaps thou
speakest truth.")
|
|
|
|
| Re: iplot, /xlog [message #49875 is a reply to message #49874] |
Fri, 18 August 2006 18:52  |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Kenneth P. Bowman writes:
> A more basic problem is that PLOT uses XLOG and YLOG, while iPlot uses
> X_LOG and Y_LOG. Not the best human factors engineering.
>
> Keywords may be slightly more consistent in the iTools, but explain
> NO_SAVEPROMPT. Why isn't that NO_SAVE_PROMPT?
I didn't say I could explain it. Only that I choose
to see it as part of IDL's charm. How else could you
remain sane?
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. (Opata Indian saying, meaning "Perhaps thou
speakest truth.")
|
|
|
|
| Re: iplot, /xlog [message #49876 is a reply to message #49875] |
Fri, 18 August 2006 18:30 |
Kenneth P. Bowman
Messages: 585
Registered: May 2000
|
Senior Member |
|
|
In article <MPG.1f4fd09a6d1b6864989c8c@news.frii.com>,
David Fanning <davidf@dfanning.com> wrote:
> Benjamin Hornberger writes:
>
>> IDL> iplot, findgen(10), xrange=[1.,10.], yrange=[2.,8.], /xlog, /ylog
>
> Try X_LOG and Y_LOG keywords and I think you will have better luck. :-)
>
> Cheers,
>
> David
>
> P.S. This is a problem with keyword inheritance. It is easy to
> write code that allows you to use the wrong keywords without
> error, but also without effect. At the end of the chain, there
> should be a _STRICT_EXTRA=extra statement to catch this kind
> of thing.
A more basic problem is that PLOT uses XLOG and YLOG, while iPlot uses
X_LOG and Y_LOG. Not the best human factors engineering.
Keywords may be slightly more consistent in the iTools, but explain
NO_SAVEPROMPT. Why isn't that NO_SAVE_PROMPT?
Ken
|
|
|
|
| Re: iplot, /xlog [message #49882 is a reply to message #49876] |
Fri, 18 August 2006 14:41 |
Michael Galloy
Messages: 1114
Registered: April 2006
|
Senior Member |
|
|
David Fanning wrote:
> P.S. This is a problem with keyword inheritance. It is easy to
> write code that allows you to use the wrong keywords without
> error, but also without effect. At the end of the chain, there
> should be a _STRICT_EXTRA=extra statement to catch this kind
> of thing.
I agree this is a major pain with the iTools. I think the problem is
that the iTool creation routine passes the keywords to multiple other
routines. In this case _STRICT_EXTRA can't be used on any individual
call since the a given keyword might be accepted in some other call.
Mike
--
www.michaelgalloy.com
|
|
|
|
| Re: iplot, /xlog [message #49883 is a reply to message #49882] |
Fri, 18 August 2006 14:36 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Benjamin Hornberger writes:
> Damn, I was reading the documentation so many times and still missed it.
> Yes, they should make sure wrong keywords are caught.
It is probably not as easy as I suggested it might be
to solve. Unless you have some final object that is
contained in all other others (e.g., the CatAtom object
in my Catalyst Library), you can never be absolutely
sure you ARE at the end of the chain. This is just
an inherent problem with multiple inheritance chains,
I think. iPlot is complicated. Lots of keywords are
inherited. It is a BIG job to keep track of all of them.
Keyword inheritance is used to keep the job under budget,
but there are risks to using it. Risks I think even I
would take, under the circumstances.
> Plus, the direct
> graphics PLOT routine takes /xlog and /ylog. Plus, the iPlot keywords
> are quite inconsistent in whether or not they have the _ after XYZ.
Oh, well, Benjamin. I think you have worked with IDL
long enough that *these* modest annoyances shouldn't
throw you. You are just probably having a bad day. Go get
a beer and worry about it next week. :-)
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. (Opata Indian saying, meaning "Perhaps thou
speakest truth.")
|
|
|
|
| Re: iplot, /xlog [message #49886 is a reply to message #49883] |
Fri, 18 August 2006 13:49 |
Benjamin Hornberger
Messages: 258
Registered: March 2004
|
Senior Member |
|
|
David Fanning wrote:
> Benjamin Hornberger writes:
>
>
>> IDL> iplot, findgen(10), xrange=[1.,10.], yrange=[2.,8.], /xlog, /ylog
>
>
> Try X_LOG and Y_LOG keywords and I think you will have better luck. :-)
>
> Cheers,
>
> David
>
> P.S. This is a problem with keyword inheritance. It is easy to
> write code that allows you to use the wrong keywords without
> error, but also without effect. At the end of the chain, there
> should be a _STRICT_EXTRA=extra statement to catch this kind
> of thing.
>
Damn, I was reading the documentation so many times and still missed it.
Yes, they should make sure wrong keywords are caught. Plus, the direct
graphics PLOT routine takes /xlog and /ylog. Plus, the iPlot keywords
are quite inconsistent in whether or not they have the _ after XYZ.
That helps for now -- still it would be great if somebody could shine
some light on the problem of how to control it after the creation of the
iTool, which I could use for some other stuff.
Thanks,
Benjamin
|
|
|
|
| Re: iplot, /xlog [message #49889 is a reply to message #49886] |
Fri, 18 August 2006 13:27 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Benjamin Hornberger writes:
> IDL> iplot, findgen(10), xrange=[1.,10.], yrange=[2.,8.], /xlog, /ylog
Try X_LOG and Y_LOG keywords and I think you will have better luck. :-)
Cheers,
David
P.S. This is a problem with keyword inheritance. It is easy to
write code that allows you to use the wrong keywords without
error, but also without effect. At the end of the chain, there
should be a _STRICT_EXTRA=extra statement to catch this kind
of thing.
--
David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Sepore ma de ni thui. (Opata Indian saying, meaning "Perhaps thou
speakest truth.")
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
