🚀 go-pugleaf

"Tom" <tom@net.com> wrote in message news:443b501d@newsgroups.borland.com...

> My Form code:

You should call SetWindowsHookEx() from inside the DLL's code, not the EXE's
code.  Have the DLL export two extra functions that the EXE can call to
set/remove the hook.

> MY Dll code:

You did not show your export statements.  Are you exporting the hook
function at all?

> Is this SetWindowsHookEx() ok

It does absolutely nothing to accomplish what you were originally asking
for.  You are not doing anything with the keystrokes, and you are not
discarding them.

> should I simply remove return 0 instead of
> CallNextHookEx(NULL, code, wParam, lParam) from dll?

Did you read the documentation yet?

    "To prevent Windows from passing the message to the rest of the hook
chain or to the target window procedure, the return value must be a nonzero
value."

Please go to http://www.deja.com and do a search through the newsgroup
archives.  Sample code for using global hooks has been posted many times
before.


Gambit