junbin

I created a simple DLL to do a global keyboard hook, but I was unable to communicate data between the procedure which set up the hook and the hook itself:



HHOOK hKeyboardHook = NULL;
int i = 0;


LRESULT CALLBACK KeyboardHookProc(int code, WPARAM wParam, LPARAM lParam) {
if (code < 0)
return CallNextHookEx(hKeyboardHook, code, wParam, lParam);

if (i = 0) {
MessageBox(NULL, "ERROR, DATA NOT COMMUNICATED", "ERROR", 0);
}

return 0;
}

extern "C" HHOOK CFHookKeyboard(void) {
if (!hKeyboardHook)
hKeyboardHook = SetWindowsHookEx(WH_KEYBOARD, KeyboardHookProc, (HINSTANCE)hMod, 0);

i = 1;

return hKeyboardHook;
}



Anyone knows of any fix?

Fordy

The problem you have is that each dll will have a seperate copy of hKeyboardHook......in the process of the app that creates the hook, it will be valid, but in all other instances if will be void........

Many compilers offer a global memory option for dlls - kind of like a static variable in a c++ class - you can have as many dlls running in the system as you need, but they all refer to one area of system memory.....in that shared area, you place the HHOOK

For VC++ you use;

Now every dll uses the same HHOOK......

Also add to this that the hook procedure (when called) exists in another process.........that means all shared handles (file...etc) are unusable (and you cant share them accross process boundries as you dont have a list of the processes that need them)...they way I get around this is for the launching app to open a MailSlot (CreateMailSlot()) and then create a thread to recieve messages......then I use CreateFile() in the hook dll to get a handle to the Mailslot (which is usable in my process) and write output to it.......

__________________
"If A is success in life, then A equals x plus y plus z. Work is x; y is play; and z is keeping your mouth shut."
Albert Einstein (1879 - 1955)

Board Rules