🚀 go-pugleaf

"Rodrigo" <rmorteo@eudoramail.com> wrote in message
news:400c14ed@newsgroups.borland.com...

> I want to use this handle to be notified when WM_QUIT
> messages are posted to the spawned apps

Normally, that would involve subclassing the window.  However, you cannot
subclass a window that belongs to another process.  You would have to use a
message hook instead via the SetWindowsHookEx() function, and implement your
hook procedure inside a separate DLL.

> because I need to know when they are closed (either by the
> system or by the user). ...

What about simply passing the spawned application's handle to
WaitForSingleObject() or GetExitCodeProcess() instead?  When you spawn a new
application instance, you could start a new thread for it, giving the thread
the application's process handle.  The thread could then use
WaitForSingleObject() or GetExitCodeProcess() in a loop to wait for the
spawned process to be terminated for any reason, not just from WM_QUIT
messages.  When the process is terminated, your thread could communicate
back to your main code so that it can update itself accordingly.

> I'm currently reading on Message Queues and found the
> PeekMessage function, however, I'm not sure that what I need
> can be done and how?

It cannot be used for what you are asking for.


Gambit