> and included a link to download a set of example programs.
You know what seems to be missing here? Quality control.
Here are the first two things I tried. Honestly. I don't
make this stuff up.
I went to Mark's website and read his blurb about the new
ColorTable function. I thought that was neat, so I downloaded
and installed IDL 8.2.1. The first thing I read in the
ColorTable documentation was this sort of odd description
of the Background keyword:
"Set this keyword to a string or three-element array describing the colors of the table. Default value is [0, 0, 0]."
OK, so I used the example right there in the documenation and
tried to set a yellow background keyword, since I don't really
understand what a background keyword can really be used for
in a ColorTable function. Here is what I typed:
% COLORTABLE: BACKGROUND must be a RGB triplet or string
Sigh...
Ok, so moving on, the next thing in Mark's list that caught
my eye was a new "Class Hierarchy view for viewing properties and methods of super- and subclasses." Again, a little oddly
phrased, but I just assume the documenatation writer is not
a native English speaker. I understand what he meant. And,
OK, I can definitely use that!
So, I open my cgMap object, which inherits a cgCoord object,
which inherits a cgContainer object, which inherits both an
IDL_Object and an IDL_Container object. Perfect test.
I don't know how to describe what I ended up with, but
"hierarchtical view" doesn't really do it justice. "God-awful
mis-mash" comes closer. Here is a picture of it.
Do you suppose that is what this is *suppose* to look like!?
I've got other things to do. I'm really restoring a computer
that refuses to boot and is resisting all attempts at repair.
I'm just looking at this stuff for fun and because I like to
be up-to-date on the latest catastrophies. :-)
Cheers,
David
-- David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/ Sepore ma de ni thue. ("Perhaps thos speakest truth.")
David Fanning writes:
> I've got other things to do. I'm really restoring a computer
> that refuses to boot and is resisting all attempts at repair.
> I'm just looking at this stuff for fun and because I like to
> be up-to-date on the latest catastrophies. :-)
By the way, I do note a positive development in the IDL
language itself. You can now use a START keyword with all
the INDGEN functions:
Print, Indgen(10, Start=5)
It's 7 more keystrokes than the old way of doing this:
Print, Indgen(10) + 5
But, it's a LOT more elegant! And, I'm happy the developers
are spending my maintenance dollars wisely.
Cheers,
David
-- David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/ Sepore ma de ni thue. ("Perhaps thos speakest truth.")
>> I've got other things to do. I'm really restoring a computer
>> that refuses to boot and is resisting all attempts at repair.
>> I'm just looking at this stuff for fun and because I like to
>> be up-to-date on the latest catastrophies. :-)
> By the way, I do note a positive development in the IDL
> language itself. You can now use a START keyword with all
> the INDGEN functions:
> Print, Indgen(10, Start=5)
> It's 7 more keystrokes than the old way of doing this:
> Print, Indgen(10) + 5
> But, it's a LOT more elegant! And, I'm happy the developers
> are spending my maintenance dollars wisely.
First off: MWROWRRRR!
Is that acerbic, rather than your normal good-natured, sarcasm I'm reading? :o)
That computer you're working on must be really giving you trouble....
> Is that acerbic, rather than your normal good-natured, sarcasm I'm > reading? :o)
> That computer you're working on must be really giving you trouble....
Aaaauughhhhh!
I'm thinking of going into farming. :-(
Cheers,
David
-- David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/ Sepore ma de ni thue. ("Perhaps thos speakest truth.")
David, regarding the class hierarchy, when I have one copy of the coyote graphics library on my IDL path the hierarchy works properly. However when I put two copies of the library on my path I get the behavior you are seeing.
Cheers,
Scott
Also, you can turn on the "duplicate routine warnings" feature to be alerted to the fact that you have multiple copies of a library on your path. In this case I get over 2,000 warning messages in the Problems View and warning markers on every cg* file when I have two copies of the coyote library on my path. -Scott
Scott E writes:
> David, regarding the class hierarchy, when I have one copy of the coyote graphics library on my IDL path the hierarchy works properly. However when I put two copies of the library on my path I get the behavior you are seeing.
Since I spend half my life preaching about ONE Coyote Library
on an IDL path, it would be hypocrasy of the highest degree
if I had more than that! I have only one copy of the Coyote
Library.
But, who knows. I'll try it again once I get IDL 8.2.1
installed on my completely reconfigured hard drive. :-(
Cheers,
David
-- David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/ Sepore ma de ni thue. ("Perhaps thos speakest truth.")
On Wednesday, October 3, 2012 6:05:39 PM UTC-6, David Grier wrote:
> On the plus side, the z-axis labels on 3D function graphics plots now are oriented correctly.
Hi David,
Yes, this was an unfortunate bug. However, it first appeared in 8.2 and it was fixed in 8.2.1. We're trying to be more responsive in fixing bugs, and I think this is a good example.
I'd like to go further: if a bug is reported, and it has a pro code solution (like this one), we'll try to fix it as soon as possible and I'll post a solution, either here or on my idldatapoint.com blog. Please take me up on this.
> % COLORTABLE: BACKGROUND must be a RGB triplet or string
> Sigh...
Yes, this is unfortunate. I'm in contact with the developer who wrote COLORTABLE, and since this is pro code, I'll provide an updated version as soon as possible.
> where Chris explains his rationale for adding it:
> "It's much faster to specify START than to add an offset to the indgen after you've created it."
Ah, I knew there must have been a reason for it. But,
I was feeling grumpy after the first two new things I
tried turned out poorly. I've paid a lot of money for
things I haven't been able to use in the past several
years. And, at that particular moment, the START keyword
felt a little frivolous. Sorry!
Cheers,
David
-- David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/ Sepore ma de ni thue. ("Perhaps thos speakest truth.")
> on Linux (the two OS I have available to me right now).
Well, I don't know. I'm on a Windows machine (my laptop),
running an up-to-date version of Windows 7 Professional,
and I have confirmed there is a SINGLE copy of the Coyote
Library on my IDL path, and my Workbench looks like this:
(Updated just a minute ago to give the whole Workbench, as
in your example.)
I don't know how to explain the differences. Any ideas?
My working theory is that IDL 8.x hates me, but I understand
from my therapist that software is probably not capable of
this.
Cheers,
David
-- David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/ Sepore ma de ni thue. ("Perhaps thos speakest truth.")
Is it possible that you have it on your IDL path, but then you also have all the code in an open project that is set to automatically be added to the path (IDL project properties)?
If you turn on the duplicate routine warnings feature and look in your Problems View, are there warnings? If so you can see what the conflicts are and then see where the duplicates are coming from.
Actually I see from your last screenshot that the Problems View tab is bold. That means there are warnings there. Please check it and see if the warnings there might help track down where the duplicates are coming from.
Thanks,
Scott
Scott E writes:
> Is it possible that you have it on your IDL path, but then > you also have all the code in an open project that is set > to automatically be added to the path (IDL project properties)?
No, I right-click on the coyote project and confirm that the
button that puts it on the IDL path when the project is opened
is deselected, as it should be.
> If you turn on the duplicate routine warnings feature and look in > your Problems View, are there warnings? If so you can see what > the conflicts are and then see where the duplicates are coming from.
Yes, there are warnings. Most seem be coming from the days before
the Coyote Library, when I embedded needed programs in the source
code of other programs. I get a ton of warnings about FSC_Normalize,
for example, which is in every object graphics program I wrote
prior to 2002. None of the warnings mentions anything about cgMap,
cgCoord, or cgContainer.
Thanks for looking into this.
Cheers,
David
-- David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/ Sepore ma de ni thue. ("Perhaps thos speakest truth.")
Scott E writes:
> Is it possible that you have it on your IDL path, but then > you also have all the code in an open project that is set
> to automatically be added to the path (IDL project properties)?
A thought comes to mind. Since I am VERY careful to have
only one Coyote Library directory, this coyote project is
created not in the IDL workspace, but from that one directory
on my C drive. I have both IDL 7.1.2 and IDL 8.2.1 installed
on this machine, and they both have that one directory as
a project (although in different workspaces). Do you think that has anything to do with this?
Cheers,
David
-- David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/ Sepore ma de ni thue. ("Perhaps thos speakest truth.")
Scott E writes:
> Is it possible that you have it on your IDL path, but then > you also have all the code in an open project that is set > to automatically be added to the path (IDL project properties)?
Oh, hang on! This does now appear to be my fault. I was showing
someone last week how to set up a Coyote directory from the idl-coyote
Subversion repository. I downloaded the files, then showed them how
to make that the coyote project directory. But, I had the *original* Coyote directory in my IDL path.
My apologies. I take back everything I've ever said bad
about IDL 8.x. It's a wonderful piece of software. And,
I note, that when you specify 10 colors in the new
ColorTable function, you actually get 10 colors in the
color bar. Fixing that problem has improved my IDL outlook
immeasurably! :-)
Cheers,
David
P.S. Alas, I was all set to send this message. I only had
to confirm that getting back to my original set-up solved
the problem. But, IDL is now hanging in trying to make the
coyote project from the right directory. Sigh...
I can neither kill the Project Wizard (because there is
an "active" project going on, a poor choice of words
under the circumstances), nor exit IDL (because it is
being blocked by the Project Wizard.
I'll probably be in limbo the rest of my life... :-(
-- David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/ Sepore ma de ni thue. ("Perhaps thos speakest truth.")
David Fanning writes:
> I can neither kill the Project Wizard (because there is
> an "active" project going on, a poor choice of words
> under the circumstances), nor exit IDL (because it is
> being blocked by the Project Wizard.
Seriously!? CTRL-ALT-DELETE doesnt' even help. That Project
Wizard can't be killed!! Friggin' A. And my hard disk
problem on my other computer is back after spending
the morning reinstalling software. It is a SERIOUSLY
bad day, today! :-(
Cheers,
David
-- David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/ Sepore ma de ni thue. ("Perhaps thos speakest truth.")
David Fanning writes:
> P.S. Alas, I was all set to send this message. I only had
> to confirm that getting back to my original set-up solved
> the problem. But, IDL is now hanging in trying to make the
> coyote project from the right directory. Sigh...
OK, finally got this thing unstuck and IDL restarted. I
confirm that the previous problem with Class Heirarchies
was my own damn fault! Sorry for wasting all the band width
today. :-(
Cheers,
David
-- David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/ Sepore ma de ni thue. ("Perhaps thos speakest truth.")
On Thu, 04 Oct 2012 12:07:27 -0600, David Fanning wrote:
> David Fanning writes:
>> I can neither kill the Project Wizard (because there is an "active"
>> project going on, a poor choice of words under the circumstances), nor
>> exit IDL (because it is being blocked by the Project Wizard.
> Seriously!? CTRL-ALT-DELETE doesnt' even help. That Project Wizard can't
> be killed!! Friggin' A. And my hard disk problem on my other computer is
> back after spending the morning reinstalling software. It is a SERIOUSLY
> bad day, today! :-(
It's been my experience that a quick tug on the power cord, followed by a nice cold adult beverage solves (or at least delays) most problems involving computers...
Bruce Bowler writes:
> It's been my experience that a quick tug on the power cord, followed by a > nice cold adult beverage solves (or at least delays) most problems > involving computers...
That's what Coyote has been telling me all morning. I guess
he'll get the beer while I go out to find a new hard drive. :-(
Cheers,
David
-- David Fanning, Ph.D.
Fanning Software Consulting, Inc.
Coyote's Guide to IDL Programming: http://www.dfanning.com/ Sepore ma de ni thue. ("Perhaps thos speakest truth.")
