本文介绍了如何正确钩WM_COMMAND的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我试图在一个mfc窗口中钩一个按钮点击。我使用WM_COMMAND和WM_NOTIFY.For测试,如果按钮被点击,钩子必须创建一个消息框。问题是它不会对按钮点击做出反应。
以下是对WM_COMMAND和WM_NOTIFY作出反应的代码:

I'm trying to hook a button click in a mfc window.And I used WM_COMMAND and WM_NOTIFY.For test, if the button is clicked, the hook must create a messagebox. The problem is that it doesn't react to button clicks.Here's the code for reacting to WM_COMMAND and WM_NOTIFY:

LPMSG msg = (LPMSG)lParam;

    switch( msg->message )
    {
    case WM_COMMAND:
        MessageBox( NULL,"HOOK","YOOOO",MB_ICONEXCLAMATION );
        break;
    case WM_NOTIFY:
        MessageBox( NULL,"HOOK","YOOOOO",MB_ICONEXCLAMATION );
        break;
    }

这里是hole dll的代码:

And here's the code to hole dll:

#include <Windows.h>
#include "FindingWindow.h"
#pragma comment( linker,"/SECTION:.SHARED,RWS" )
#pragma data_seg( ".SHARED" )
CaptureTextWindow* ctw;
HHOOK hook = 0;
HMODULE hInstance = 0;
HWND hWndServer = NULL;
#pragma data_seg()

static LRESULT CALLBACK msghook(int nCode, WPARAM wParam, LPARAM lParam);
__declspec(dllexport) BOOL clearMyHook(HWND hWnd);

BOOL APIENTRY DllMain( HINSTANCE hInst, DWORD ul_reason_for_call, LPVOID lpReserved )
{
    switch( ul_reason_for_call )
    {
    case DLL_PROCESS_ATTACH:
        hInstance =  hInst;
        return TRUE;
    case DLL_PROCESS_DETACH:
        if(hWndServer != NULL)
          clearMyHook(hWndServer);
        return TRUE;
    }
    return TRUE;
}



__declspec(dllexport) BOOL WINAPI setMyHook(HWND hWnd)
  {
   if(hWndServer != NULL)
      return FALSE;
   hook = SetWindowsHookEx(
                           WH_CALLWNDPROC,
                           (HOOKPROC)msghook,
                           hInstance,
                           0);
   if(hook != NULL)
   { /* success */
      hWndServer = hWnd;
      return TRUE;
   } /* success */
   return FALSE;
}
__declspec(dllexport) BOOL clearMyHook(HWND hWnd)
{
    if(hWnd != hWndServer)
       return FALSE;
    BOOL unhooked = UnhookWindowsHookEx(hook);
    if(unhooked)
       hWndServer = NULL;
    return unhooked;
}

static LRESULT CALLBACK msghook( int nCode,        // hook code
                                   WPARAM wParam ,  // message identifier
                                   LPARAM lParam )
{
    if( nCode < 0 )
    {
        CallNextHookEx( hook, nCode, wParam, lParam );
        return 0;
    }
    LPMSG msg = (LPMSG)lParam;

    switch( msg->message )
    {
    case WM_COMMAND:
        MessageBox( NULL,"HOOK","YOOOO",MB_ICONEXCLAMATION );
        break;
    case WM_NOTIFY:
        MessageBox( NULL,"HOOK","YOOOOO",MB_ICONEXCLAMATION );
        break;
    }

    return CallNextHookEx( hook, nCode, wParam, lParam );
}

我不仅使用WM_COMMAND原因我认为mb会工作,但它didn

I used not only WM_COMMAND cause I thought mb it will work, but it didn't.Thanks for answer.

推荐答案

lParam a href =http://msdn.microsoft.com/en-us/library/windows/desktop/ms644975.aspx =nofollow> WH_CALLWNDPROC hook 的类型为。 CallWndProc 应如下所示:

The lParam for a WH_CALLWNDPROC hook is of type CWPSTRUCT. Your CallWndProc should look like this:

// ...
const CWPSTRUCT& cwps = *(CWPSTRUCT*)lParam;
switch ( cwps.message ) {
case WM_COMMAND:
    MessageBox( ... );
    break;
// ...

这篇关于如何正确钩WM_COMMAND的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

09-03 14:01