🚀 go-pugleaf

> The hook DLL is injected into the address space of every application(s)
that
> you are hooking.  Unless the calling application currently has focus, it
> can't bring any windows into focus.  This way whatever the user is
currently
> doing is not interrupted.
>
> It could also be caused your use of a static HWND, since every DLL
instance
> is going to get its own local copy of the HWND, but you are only setting
the
> HWND for the DLL instance that is loaded by your own application.  If you
> look at the function's return value, I will bet you that it is reporting
an
> invalid handle.  To share an HWND (or anything else, for that matter)
> between all of the instances of your DLL, you need to store the data in
> shared memory.  Look at the CreateFileMapping() and MapViewOfFile()
> functions for that.

You're right about getting an invalid handle.

>but you are only setting the HWND for the DLL instance that is loaded by
your own application

I understand, of course, but should that be a problem with my application?
As to me I think I don't use more than this one instance being loaded by my
application. Am I right?

So I tried another idea by creating a callback function in my main
application that is called from the DLL's GetMsgProc function.

My callback function type definition:
    typedef void CALLBACK (*MOUSE_EVENT_CALLBACK_FUNCTION)(void)

Inside DLL:
    static MOUSE_EVENT_CALLBACK_FUNCTION MyMouseCallbackFunction;

I first hand over the callback function address to the static DLL variable
'MyMouseCallbackFunction'. This works fine.
Now when I mouseclick OUTSIDE my Borland application the
'MyMouseCallbackFunction' value inside the DLL is NULL.

So again, I still don't get the picture why a system call of  my DLL
'GetMsgProc' function (being the SAME instance, loaded by my application)
looses my static DLL variable values as I thought that STATIC means the
variable is kept alive as long as my application is active. Or do I miss or
mix something?

Henk