Re: key strokes intercept

[tmoran@bix.com (Tom Moran)]

>>KeyDown, KeyUp, KeyCode etc are Windows events. Visual Basic provides
>>a nice framework for handling events nicely. Plain Ada does not; you
>>need a thick binding to Windows
>So right now there's no way to do what I want if I'm writing a DOS
>program ?  I have maybe two weeks to get it into my program if I
>decide that I want to try.  I'd use it as part of a password input
>procedure, you know the asterix replacing whatever is typed in at the
>keyboard.
>... replace the
>key code (or whatever I`ll have to play with) with the backspace
>followed by the asterix, if I can't actually turn off the screen ECHO
No - there was just confusion about what you want.  The KeyDown etc VB
events are quite unnecessary for your password entry.  Use the
Get_Immediate as you plan, or, in DOS, use the DOS call to get a
character with no echo (see your compiler's vendor supplied library to
see how to make int21 or BIOS calls with your compiler).  
  The event approach is normally used in Windows and is most easily
done there using one of the thick Ada bindings.  You can also do it
using a separate task in DOS, but that's major overkill for password
entry.