| Re: Command input window in Windows: why only one line? Why, generally does the windows handling not work? [message #17828] |
Tue, 16 November 1999 00:00 |
Kristian Kjaer
Messages: 58
Registered: June 1998
|
Member |
|
|
> Kristian Kj�r <Kristian.Kjaer@Risoe.Dk> wrote:
>> There are several other flaws in the (5.x) windows port which are
>> perhaps somehow related:
>>
>> ) It is not possible, using the keyboard, to change focus to any
>> open *.pro file. You have to use the mouse.
Jonas wrote:
> ctrl+tab
> or
> f6 shift+f6
>
> Jonas
Thanks, Jonas, this is what I'd normally do in any other windows
program.
However, try this:
ctrl(W) ; puts focus on command line: Works.
IDL> .ed prog1
IDL> .ed prog2
IDL> .ed prog3 ; Now focus is in the prog3.pro window, and you can move
the cursor around in it with the arrows, highlight with shift(arrow),
copy with ctrl(C), etc.: Fine
ctrl(W) ; puts focus back on the command line: Works.
ctrl(tab) ; Apparently changes focus between the editor windows,
but you don't have the cursor there. It is still on the command line, so
you cannot highlight with shift(arrow), copy with ctrl(C), etc.: Not so
good.
Also, strangely, the output log is not a 'window' on a par with the
other windows. To get focus on it, you have to click in it with the
mouse. Only then can you maneuvre in it with the keyboard.
- Kristian
|
|
|
|
| Re: Command input window in Windows: why only one line? Why, generally does the windows handling not work? [message #17838 is a reply to message #17828] |
Tue, 16 November 1999 00:00  |
Jonas
Messages: 23
Registered: May 1998
|
Junior Member |
|
|
Kristian Kj�r <Kristian.Kjaer@Risoe.Dk> skrev i
diskussionsgruppsmeddelandet:382F094A.E7F18FE7@Risoe.Dk...
> Bigorna wrote:
>> I find one irritating feature in IDL for Windows, relative to the Unix
>> and Linux versions: it is not possible to paste multiple lines of code
>> into IDL!
>
> If it is any consolation, I completely agree with you.
>
> There are several other flaws in the (5.x) windows port which are
> perhaps somehow related:
>
> ) It is not possible, using the keyboard, to change focus to any
> open *.pro file. You have to use the mouse.
ctrl+tab (works in almost all windows programs except MS word that uses
ctrl+f6)
or
f6 shift+f6
Jonas
|
|
|
|
| Re: Command input window in Windows: why only one line? Why, generally does the windows handling not work? [message #17860 is a reply to message #17828] |
Sun, 14 November 1999 00:00 |
Kristian Kjaer
Messages: 58
Registered: June 1998
|
Member |
|
|
Bigorna wrote:
> I find one irritating feature in IDL for Windows, relative to the Unix
> and Linux versions: it is not possible to paste multiple lines of code
> into IDL!
If it is any consolation, I completely agree with you.
There are several other flaws in the (5.x) windows port which are
perhaps somehow related:
) It is not possible, using the keyboard, to change focus to any
open *.pro file. You have to use the mouse.
) It is not possible, using the keyboard, to change focus to the
output log. You have to use the mouse.
) Worst, during long computations (or long whatever) the IDL window
is not updated. This means that if, during the long computation,
you have covered the IDL window by another window, then if you
try to put focus back on the IDL window, you don't get to see any
output that IDL may have produced in the meantime
and which might help you to decide whether or not to let the
computation continue.
And, if you've programmed something like "Press key 'N' to Not
continue", then after changing focus away from IDL, you cannot
get into a state where you can get IDL to listen to your 'N'.
BTW, IDL4 for windows didn't have these problems.
- Kristian
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
