🚀 go-pugleaf

Each control on a window has it's on HWND.  You find the edit controls
HWND using EnumChildWindows enumeration API, passing the parent window
handle along with a callback function that evaluates each child HWND.
You'll need to test to see which child is the edit control, because
each and every control that the parent window owns will be enumerated.
They'll always be passed in the same sequence, so its not so tough.

Once you have your edit control's HWND, you SetWindowsHookEx on that.
Intercept till your hearts content.



On Thu, 18 Nov 2004 19:10:09 -0800, CC wrote:

> 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