From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,511884c4d439ef8 X-Google-Attributes: gid103376,public From: tmoran@bix.com (Tom Moran) Subject: Re: key strokes intercept Date: 1999/04/01 Message-ID: <3703c918.218348@news.pacbell.net>#1/1 X-Deja-AN: 461678995 References: <370160f9.569041534@news.dsuper.net> <3705227f.749682976@news.dsuper.net> X-Complaints-To: abuse@pacbell.net X-Trace: typhoon-sf.pbi.net 922995483 206.170.2.178 (Thu, 01 Apr 1999 11:38:03 PST) Organization: SBC Internet Services NNTP-Posting-Date: Thu, 01 Apr 1999 11:38:03 PST Newsgroups: comp.lang.ada Date: 1999-04-01T00:00:00+00:00 List-Id: >>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.