Re: Terminating a program

brian sharon wrote:

 > Sounds like you might be better off not using WM_CLOSE, since the OS 
is going to complain if you ignore it for too long.  But you have plenty 
of other options if you want to handle communications between two apps 
you control.  Easiest thing is to use RegisterWindowMessage() to get a 
unique message value for your own custom quit message, and then the 
child application could post WM_CLOSE to itself whenever it receives 
that custom quit message from the launcher app.
 >


Results from this seem very promising. I did add TerminateProcess as the
fallback, but so far (after doing one fix to the graphical program), I
have not yet seen it triggered.

(I have previously terminated programs on this setup (Nvidia +
WindowsXP) and I have not noticed any ill effects)

     Thanks for your and Jon's comments


             Eero

PS. I first sent this using wrong address, moderator please kill
that message...



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Gamedevlists-windows mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gamedevlists-windows
Archives:
http://sourceforge.net/mailarchive/forum.php?forum_id=555