🚀 go-pugleaf

Hi,
thanks for your help!

> Just be careful with PostMessage().  Keep in mind that it returns
> immediately...

Thanks for the hint. I guess that is why I would prefer SendMessage(). On
the other hand with PostMessage() I maybe could implement a timeout
mechanism. I think it depends on the individual message. So it would be nice
to have both options.

> > The hook callback is called for other messages (redraw
> > etc.)
>
> Those are posted to the message queue, thus the WH_GETMESSAGE hook would
> pick them up.
>
> > but never for my SendMessage().
>
> Did you call SetWindowsHookEx() a second time to register the
WH_CALLWNDPROC
> hook as well?
>

Actually I have tried both ways separately yet. But I should do both in the
end. As I wrote the client calls SetHook(threadId) on the DLL which
currently looks like this:

bool SetHook(DWORD threadId)
{
   hHook = SetWindowsHookEx(WH_CALLWNDPROC, (HOOKPROC)CallWndProc,
HInstance, threadId);

   if(hHook == NULL)
      return false;
   else
      return true;
}

I'm a little unsure about the parameters passed to SetWindowsHookEx? Must
the third parameter be NULL or not in my special case?

The callback in the DLL looks like this:

LRESULT CALLBACK CallWndProc(int code, WPARAM wParam, LPARAM lParam)
{
   if(code == HC_ACTION)
   {
      CWPSTRUCT* msg = (CWPSTRUCT*)lParam;
      switch(msg->message)
      {
         case HOOK_WM_TEST:
            MessageBeep(-1);   //never called ##########
         break;
         case WM_NCHITTEST:
            MessageBeep(-1);  //this is always called when I move the mouse
over the server window########
         break;
      }
   }

   return CallNextHookEx(hHook, code, wParam, lParam);
}


the call in the client looks like this:

void __fastcall TForm2::Button2Click(TObject *Sender)
{
      if(hwnd) //hwnd returned from FindWindow for the servers main window
      {
         SendMessage(hwnd, HOOK_WM_TEST, 0, 0);
      }
}

I really don't have any idea what could be wrong?
thanks,
Nick