🚀 go-pugleaf

Hi Remy - Thanks for the info - I almost follow you -

I understand the part about the application sending custom msg, and the dll
hook function intercepting that message.

That would at least tell the dll that the application->control is active to
receive messages (edit boxes receiving key messages, etc).

Is there anyway for the dll hook function to distinguish which of many
controls a particular message is coming from?

For example - the edit box I want to record info from could receive a msg,
then the user goes to another box, then jumps back to the box I'm interested
in, the recording seems to get jumbled up - which box was a particular key
stroke message  intended for?

I know I  missing something still - but its a little clearer.

Thanks very much,
CurtC


"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message
news:419cf263$1@newsgroups.borland.com...
>
> "CC" <nospammer@aol.com> wrote in message
> news:419cdca5$1@newsgroups.borland.com...
>
> > I would like to monitor the keystrokes in a control in another app.
> >
> > I understand the SetWindowHookEx() needs to be in a .dll
>
> Yes.
>
> > I'm wonding how to make the association between establishing
> > a hook to another application, and then in that application to
> > an edit box (for example).
>
> Have both your own application and the DLL register a custom message via
> RegisterWindowMessage().  Then have the DLL set up a message hook as
needed.
> Your application can then call the DLL to load the hook, then use
> FindWindow() and such to located the desired child window in the other
> application, and then post the custom message to that control.  When the
DLL
> gets the message, it can begin monitoring the child window as needed.
>
>
> Gambit
>
>