1. Interesting problem with DOS32 prog in Windows Box
Here's an interesting problem for fellow Euphorian's to have a go at
solving - it is a real problem and not one I've thrown up just for the
hell of it ...
I am writing a text editor, in Euphoria of course, that I run at an
MS-DOS prompt in a Win95 MS-DOS prompt box.
When the use depresses the ALT key a menu pops. It then disappears after
the user presses another key ( with or without releasing the ALT key )
having done what the user wants doing.
Of course, under Win95 ( + 98 / NT ? ), ALT-SPACE, ALT-TAB etc switch
from the MS-DOS prompt window to the desktop, another App and so on; the
MS-DOS window is reduced to a splot on the TaskBar.
My menu pops up as soon as the user depresses ALT and if it is ALT-SPACE
etc, then when the MS-DOS prompt window is next selected the popup menu
is still 'on screen'.
It would be nice to get rid of the popup when my program loses focus.
I've tried an inactivity timeout but this doesn't seem to work and isn't
very nice as a solution as one can come back too soon or take too long
pressing an ALT+n sequence. Using get_keys() etc, the ALT-SPACE and
others aren't even seen, nor can they be spotted in the BIOS/MS-DOS
keyboard ring buffer as far as I could tell.
Any solutions ? [ Remember this is a DOS32 program and not a WIN32 app.
]
2. Re: Interesting problem with DOS32 prog in Windows Box
If you are wondering how to disable key combinations like ALT-SPACE, look
at the properties of the DOS window or your program. Under Misc, select
which keys you want to enable.
Jeffrey Fielding
JJProg at cyberbury.net
3. Re: Interesting problem with DOS32 prog in Windows Box
>
>If you are wondering how to disable key combinations like ALT-SPACE, look
>at the properties of the DOS window or your program. Under Misc, select
>which keys you want to enable.
>
>Jeffrey Fielding
>JJProg at cyberbury.net
Thanks for the suggestion, but ...
I'd actually like to keep the ALT-SPACE keys etc working so I can
quickly swap between MS-DOS and Win95. The bottom line problem is, I
suppose, how to detect in an MS-DOS proggy when it has lost focus to the
Big Nasty GUI so it can respond to that event ( even when its response
isn't immediately seen ).
