| Lose control of IDL window [message #23384] |
Wed, 24 January 2001 07:54  |
philippe_fischer2000
Messages: 1
Registered: January 2001
|
Junior Member |
|
|
I have recently switched from using IDL in a UNIX environment to
Windows2000 (not my choice!). When running a job in the idlde I lose
control of the window while the job is running. I regain control once
the job finishes. By lose control I mean I cannot maximize the window
(if I have minimized from the toolbar), I cannot view output in the
window and I cannot "break" out of the job. If I try to put the cursor
over the idlde window it disappears. An example of job that causes this
problem is:
for i=1L,1000000 do print,'hi'
Has anybody encountered this problem? I have been corresponding with
somebody at RSI but he hasn't come up with any solutions yet.
Regards,
Phil
Sent via Deja.com
http://www.deja.com/
|
|
|
|
| Re: Lose control of IDL window [message #23515 is a reply to message #23384] |
Thu, 25 January 2001 08:43  |
Pavel A. Romashkin
Messages: 531
Registered: November 2000
|
Senior Member |
|
|
Med Bennett wrote:
>
> I think it's crazy, though, that IDL doesn't give you any way of killing an
> out-of-control process.
Sure there's a way. I use it all the time. Its a Reset button. A lot
faster than trying all other ways first.
Cheers,
Pavel
|
|
|
|
| Re: Lose control of IDL window [message #23520 is a reply to message #23384] |
Thu, 25 January 2001 04:13 |
davidf
Messages: 2866
Registered: September 1996
|
Senior Member |
|
|
Med Bennett (mbennett@indra.com) writes:
> I think it's crazy, though, that IDL doesn't give you any way of killing an
> out-of-control process. I have had situations where I have made a programming
> error that resulted in an infinite loop, and there was no way short of killing
> IDL to get out, thus losing (possibly) unsaved work. Way back in IDL 4.x (?)
> you could do a Ctrl-Break or something that would save you in such cases, but no
> longer.
Windows processes can be interrupted with a Control-Break.
But, of course, there are things you can interrupt and
things you can't. An infinite FOR loop is trouble because
the FOR loop is treated as a single command by the IDL
compiler and IDL only checks for interrupts at the *end*
of each command. In this regard, it doesn't matter whether
you are running a Windows version or a UNIX version!
Cheers,
David
--
David Fanning, Ph.D.
Fanning Software Consulting
Phone: 970-221-0438 E-Mail: davidf@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
