How to catch WM_CLOSE by using hook

[N Q H]

Hi all, I have written a program which can monitor a specific program when it was closed.I used hook to do it and everything seem be ok but the problem is that I cannot hook WM_CLOSE message. I have tried to use WH_GETMESSAGE, WH_CBT, WH_CALLWNDPROC. But all of them seem not work properly! here is my code:

hHook = SetWindowsHookEx(WH_CALLWNDPROC,fnHookProc,hInstDLL,tid);

DLLEXPORT LRESULT CALLBACK KeyboardProc(int nCode,WPARAM wParam, LPARAM lParam)
{

LPMSG msg = (LPMSG)lParam;

   if(msg->message == WM\_CLOSE )
   {
	  //do somethings here
	
   }

   return CallNextHookEx(\_hHook,nCode,wParam, lParam);

}

anybody help me. thanks

[N][Q][H]

[David Crow]

There must be something special about the WM_CLOSE message. Are you using a DLL? Are you calling SetWindowLong() in that DLL? Are you injecting the DLL into the process of the "specific window?"

"Old age is like a bank account. You withdraw later in life what you have deposited along the way." - Unknown

"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons

[Naveen]

[N][Q][H] wrote:

DLLEXPORT LRESULT CALLBACK KeyboardProc(int nCode,WPARAM wParam, LPARAM lParam)

You hook handler seems to be incorrect. For instance if you are using the WH_CALLWNDPROC, the handler should be like

LRESULT CALLBACK CallWndProc(int nCode,WPARAM wParam, LPARAM lParam)
{
PCWPSTRUCT msg = (PCWPSTRUCT)lParam;

   if(msg->message == WM\_CLOSE )
   {
	  //do somethings here
	
   }	
   return CallNextHookEx(\_hHook,nCode,wParam, lParam);

}

nave [OpenedFileFinder] [My Blog]

[N Q H]

ok, KeyboardProc must be renamed to fnHookProc. But this is not the cause. This just a mistake when I copy from my code.

LRESULT CALLBACK LRESULT CALLBACK fnHookProc(int nCode,WPARAM wParam, LPARAM lParam)
{
PCWPSTRUCT msg = (PCWPSTRUCT)lParam;

   if(msg->message == WM\_CLOSE )
   {
	  //do somethings here
	
   }	
   return CallNextHookEx(\_hHook,nCode,wParam, lParam);

}

[N][Q][H]

[N Q H]

Because this is a global hook which will monitor all message before they really reach to target window. So I think It doesn't need inject the dll to the target window. But I will try. I took a round from google and know that many people have the same problem with me when they try to catch the WM_CLOSE. But I still cannot find the solution.

[N][Q][H]

[Lost User]

It's an old Win32 FAQ (see onWin32 grp[^]) (same method than on Win 9x)