S
Stelrad Doulton
Hi,
I am after pointers towards the best strategy for raising events in one
application as a result of a condition in another application, there will be
about 10 event types and they will have to fire in both directions. The
purpose of this is to provide a class for managing another application so
one half of this process is taking place within a dll.
I started by looking at creating MessageWindow within the dll but found that
there was no reliable way to get a handle to it from another application. I
may be wrong on this but I found that I could not set the Window Caption,
therefore I could only supply the class name to FindWindow which is
dangerous as there could be other MessageWindows about.
I have also looked at I have looked at Alex Yakhin's MemoryMapping code but
I don't think its really what I was after.
Thanks
I am after pointers towards the best strategy for raising events in one
application as a result of a condition in another application, there will be
about 10 event types and they will have to fire in both directions. The
purpose of this is to provide a class for managing another application so
one half of this process is taking place within a dll.
I started by looking at creating MessageWindow within the dll but found that
there was no reliable way to get a handle to it from another application. I
may be wrong on this but I found that I could not set the Window Caption,
therefore I could only supply the class name to FindWindow which is
dangerous as there could be other MessageWindows about.
I have also looked at I have looked at Alex Yakhin's MemoryMapping code but
I don't think its really what I was after.
Thanks