| Re: A couple of IDL for NT questions [message #10295] |
Tue, 11 November 1997 00:00 |
davidf
Messages: 2866
Registered: September 1996
|
Senior Member |
|
|
Peter Webb (peter_webb@hpl.hp.com) writes:
> As someone who has recently started using IDL on an NT platform after a
> few years on Unix, I have a couple of annoyances. If they are fixable,
> I'd be grateful to hear how!
>
> 1. To type commands, the mouse has to be clicked in that tiny little
> window at the bottom of the screen. I'd prefer that the prompt received
> mouse focus whenever nobody else has it, e.g. if I click in the command
> log, I can't type there, so why not give me a useful focus? Does anyone
> actually prefer the splitting of the command prompt from the command
> log?
I would prefer that if I clicked in the command log window that I
am put into the command input window, but a Control-W gets me into
the command input window pretty quickly if my hands are too shaky
to point correctly.
> 2. Is there some way of automatically running main level scripts? Sort
> of like shift F5, but issue a .run. I'd use this all the time! and I'd
> care less about number 1 above.
Shift-F5 works on my NT machine. You can also click that funny
button in the middle of the command buttons that looks like a
stack of books with a blue thermometer. This can't be right, but
I don't know what the folks at RSI had in mind here. I love the
stack of books that has the yellow starburst on it. I use it all
the time to compile my programs. :-)
> 3. This is the biggy. Once I've started a calculation, and realized I
> started it wrong, how do I kill it? I used to just type Control-C, but
> this apparently has no effect. The only way to kill a run-away loop is
> via the NT task-manager?
Try Control-Break. That is the interrupt key combination.
> P.S. And while I'm at it, I've been using VB 5.0 lately, and I've really
> gotten to like the flyover variable values when stopped at a breakpoint.
> Makes checking out a bunch of variably values *very* fast. Maybe in
> 6.0?
I'm not familiar with this, but I like the way you can select
a variable and click the Print Variable macro and gets its
value printed out. I imagine it wouldn't be too hard to write
your own macro for "print all local variables", or whatever.
Cheers,
David
-----------------------------------------------------------
David Fanning, Ph.D.
Fanning Software Consulting
E-Mail: davidf@dfanning.com
Phone: 970-221-0438
Coyote's Guide to IDL Programming: http://www.dfanning.com/
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
