| Re: What is going on with the minor ticks on log plots????? [message #12583 is a reply to message #12579] |
Wed, 26 August 1998 00:00   |
Joe[2]
Messages: 11 Registered: May 1998
|
Junior Member |
|
|
> Joe (Post.Reply@This.News.Group) writes:
>
>> I'm running v5.1 under NT and have noticed the following bad
>> behavior. While using the /XLOG key along with even powers of
>> 10 for XRANGE and XTICKS set to the proper number of decades
>> and xminor set to zero. I either do or do not get the expected
>> minor ticks at (2,3,4,5,6,7,8,9). After some experimentation, it
>> became apparent that the range specified by XRANGE had to
>> fall wholly within the range from 1.000 to 1.e10.
>>
>> That is
>> plot,[1],/nodata,/xlog,xrange=[1,1000],xticks=3,xminor=0
>> works, but
>> plot,[1],/nodata,/xlog,xrange=[0.1,100],xticks=3,xminor=0
>> plot,[1],/nodata,/xlog,xrange=[1.e8,1.e11],xticks=3,xminor=0
>> do not!
>>
>
> I am running Windows NT 4, SP3 on my machine and I find that
> all three of these commands work correctly in both IDL 5.1 and
> IDL 5.1.1. Could this be a graphics driver problem?
>
> Cheers,
>
> David
Dave,
Thanks for noticing this. Hmmm, Works here now too! Each
of these commands work if I type them in a new IDL session, but
fail after I run a particular program. This is obviously a bit more
subtle of a problem. I'll try and reproduce the problem and submit
the code for review.
New topic: Why does IDL v 5.1 nolonger CD to the source directory
of a .pro file when I double click on it from the explorer, but does if
I use the IDL:file:open menu to open it? If this is an intentional shift
in operating standards - I do not like it. I lose track of my postscript
file output now (ends up in the the IDL Source tree root directory).
More in a bit,
JMZ
|
|
|
|