🚀 go-pugleaf

"Henk" <h.van.winkoop@wxs.nl> wrote in message
news:4076476e$1@newsgroups.borland.com...

> I understand, of course, but should that be a problem
> with my application?

Yes.  You are trying to intercept events from an external process, which
means that a separate and independant instance of your DLL must be injected
into that process in order to hook that process.  Setting the HWND for the
instance of the DLL that is injected into your own application will have no
effect on the values of other instances of the DLL that are injected into
other processes.  Thus the need to set asside a block of shared memory so
that they can all share the same HWND and HHOOK values.

> As to me I think I don't use more than this one instance being
> loaded by my application. Am I right?

Your application has an instance loaded, but so does every other process
have its own instance automatically loaded by the OS.

> So I tried another idea

I already told you what you need to do - use shared memory via
CreateFileMapping() and MapViewOfFile().

> by creating a callback function in my main application
> that is called from the DLL's GetMsgProc function.

That will not solve the problem.  That will only effect the DLL instance
that is loaded by your own application.  It will have no effect on the other
instances loaded by other processes at all.

> I first hand over the callback function address to the static
> DLL variable 'MyMouseCallbackFunction'. This works fine.

You are still missing the point.  Static values are NOT global across
multiple processes.  Every process will get its own separate and independant
instance of the DLL loaded, each with its own local variables.  Setting the
variables of one instance will have no effect on the other instances at all.

> Now when I mouseclick OUTSIDE my Borland application
> the 'MyMouseCallbackFunction' value inside the DLL is NULL.

Correct, for the reasons explained above.


Gambit