Xref: utzoo comp.windows.ms:2392 comp.os.os2:1603
Newsgroups: comp.windows.ms,comp.os.os2
Path: utzoo!utgpu!watserv1!maytag!watdragon!tiger!gpsteffler
From: gpsteffler@tiger.uwaterloo.ca (Glenn Steffler)
Subject: Re: no-echo input
Message-ID: <1990May30.192043.3281@watdragon.waterloo.edu>
Sender: daemon@watdragon.waterloo.edu (Owner of Many System Processes)
Organization: University of Waterloo
References: <102@bohra.cpg.oz> <1584@ns-mx.uiowa.edu>
Date: Wed, 30 May 90 19:20:43 GMT
Lines: 21

In article <102@bohra.cpg.oz> ejp@bohra.cpg.oz.au (Esmond Pitt) writes:
>I asked this a while ago but apparently it didn't get transmitted upstream.
>
>Is it possible to accept input without echo (e.g. password fields) under:
>
>	(1) MS-Windows
>	(2) PM
>
>and if so, how?
I can give you a hint for Windows:

An easy way to get no-echo input is to capture the edit control message that
informs you of a new key press.  Simply acknowledge the key stroke, but 
replace it with an 'x' or whatever...

I don't have the SDK in front of me, but I believe the EN_ messages notify
the program of any edit control changes.  Just use a SetWindowText() command
to set the text to all 'x's (for the number of char's entered).

----
Co-Op Scum