|
|
| Re: Is your IDL5.4 windows interface flaky too? [message #26401 is a reply to message #26400] |
Thu, 30 August 2001 14:14  |
mvukovic
Messages: 63
Registered: July 1998
|
Member |
|
|
Steve Hartmann <s.l.h@badspam.home.com> wrote in message news:<7oSOO8iD8n9foBe9R+Xk2NtOBx6k@4ax.com>...
> Mirko Vukovic (mvukovic@taz.telusa.com) writes:
>
>> It it me, or the IDLDE (development environment, I guess) of IDL 5.4
>> on windows NT is flaky.
>>
>> I only recently installed 5.4, and every once in a while I cannot set
>> or clear a breakpoint.
>>
>
> I've had problems with this in the last three versions of IDL under NT
> and now with Win2K. I can usually *set* the breakpoints ok, but many
> times they get removed while the colored dot does not. Of course, then
> the program just zooms on past this line. This often happens when I
> have added or deleted some lines of code. Now I usually go to the
> "Edit Breakpoints" window (launched by the icon with the 4 red dots)
> and clear all points and reset them where I want them. Kind of a pain
> but better than crossing my fingers for a breakpoint stop.
Thanks, I have completely forgotten about that one. Off course, I
could go back to the old days and use the breakpoint command:-)
>
>>
>> The variable watcher is out of step most of
>> the time, and ctrl-W that is supposed to move the cursor to the
>> command window sometimes fails.
>>
>
> I agree with David and never use this. I find it easier to type:
> help, variable (or print, variable)
> then to search for the variable in the list.
Ahem, I only started using it now that I have a 21" monitor, and I can
splurge on open windows
>
> I've never seen ctrl-W fail. However, when a program stops at a
> breakpoint, most of the time the focus is then in the command window.
> Sometimes it's in the edit window. Sometimes I don't know where it is.
> The second case is the worse for me because I'm usually half done
> typing a command before I realize I've been editing my code.
That is so frustrating. Thank god they provided for the file/revert
command.
Thanks for all the comments. BTW (David), I use Main's only to get
things going off course :-)
Mirko
|
|
|
|
| Re: Is your IDL5.4 windows interface flaky too? [message #26402 is a reply to message #26401] |
Thu, 30 August 2001 11:38 |
Steve Hartmann
Messages: 21
Registered: March 2000
|
Junior Member |
|
|
Mirko Vukovic (mvukovic@taz.telusa.com) writes:
> It it me, or the IDLDE (development environment, I guess) of IDL 5.4
> on windows NT is flaky.
>
> I only recently installed 5.4, and every once in a while I cannot set
> or clear a breakpoint.
>
I've had problems with this in the last three versions of IDL under NT
and now with Win2K. I can usually *set* the breakpoints ok, but many
times they get removed while the colored dot does not. Of course, then
the program just zooms on past this line. This often happens when I
have added or deleted some lines of code. Now I usually go to the
"Edit Breakpoints" window (launched by the icon with the 4 red dots)
and clear all points and reset them where I want them. Kind of a pain
but better than crossing my fingers for a breakpoint stop.
>
> The variable watcher is out of step most of
> the time, and ctrl-W that is supposed to move the cursor to the
> command window sometimes fails.
>
I agree with David and never use this. I find it easier to type:
help, variable (or print, variable)
then to search for the variable in the list.
I've never seen ctrl-W fail. However, when a program stops at a
breakpoint, most of the time the focus is then in the command window.
Sometimes it's in the edit window. Sometimes I don't know where it is.
The second case is the worse for me because I'm usually half done
typing a command before I realize I've been editing my code.
-Steve
|
|
|
|
| Re: Is your IDL5.4 windows interface flaky too? [message #26403 is a reply to message #26402] |
Thu, 30 August 2001 10:47 |
Pavel A. Romashkin
Messages: 531
Registered: November 2000
|
Senior Member |
|
|
David Fanning wrote:
>
> The variable watcher gave me a headache from
> the first day I used it. I turned it off and
> haven't seen it since. :-)
At least in 5.4 it does not crash IDL anymore. It is a big improvement.
In 5.2 it crashed IDL if I tried to check out a pointer value (not
always but often).
Cheers,
Pavel
|
|
|
|
| Re: Is your IDL5.4 windows interface flaky too? [message #26404 is a reply to message #26403] |
Thu, 30 August 2001 10:01 |
David Fanning
Messages: 11724
Registered: August 2001
|
Senior Member |
|
|
Mirko Vukovic (mvukovic@taz.telusa.com) writes:
> It it me, or the IDLDE (development environment, I guess) of IDL 5.4
> on windows NT is flaky.
>
> I only recently installed 5.4, and every once in a while I cannot set
> or clear a breakpoint.
I've used IDL 5.4 on Windows NT for a long time. I've
never noticed any problems setting breakpoints, although
there *is* a certain sequence you have to go through to
do it. (I don't even know what it is, I just know
it involves hitting the "compile" button frequently.)
I guess my fingers have gotten so adept at it I just
do the right thing all the time, now. :-)
> The variable watcher is out of step most of
> the time, and ctrl-W that is supposed to move the cursor to the
> command window sometimes fails.
The variable watcher gave me a headache from
the first day I used it. I turned it off and
haven't seen it since. :-)
> Finally, (and this is from 5.3 at
> least), single-stepping will not function in the MAIN routine, only
> subroutines.
What in the world are you using a main
routine for!? I thought all there were
were procedures and functions. :-)
Cheers,
David
--
David W. Fanning, Ph.D.
Fanning Software Consulting
Phone: 970-221-0438, E-mail: david@dfanning.com
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Toll-Free IDL Book Orders: 1-888-461-0155
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
