Re: [GD-Windows] Terminating a program

[<epa...@ko...>]

brian sharon wrote:

> Windows pops up that dialog box because your graphics application isn't 
> processing messages, so Windows considers the app to be hung.  You 
> should figure out why that's happening, and fix the bugs in your 
> graphics app so that it can actually process messages and shutdown cleanly.
> 


Probably true. Actually I suspect that I have two kinds of problems
here. The other is that the shutdown request can happen already at the
application startup time. I do poll the windows messages now and then
also during that time, but the application might be in an library
reading an index from a large zip resource file or something like that
which takes some time. The other problem is that sometimes this happens
during the normal run time, might be some kind of transient dead lock
with the networking code (and Visual Studio debugger is not too helpful
here)


Is there a way of delivering WM_CLOSE so that the dialog box does not
appear even if the application does not respond? With this I would
probably solve 95% of my current problem cases. (And could concentrate
my debugging effort to the remaining 5%)

-------

Regarding the message from Jon Watte:

I would probably use the TerminateProcess as my fall back as described
on: http://support.microsoft.com/default.aspx?scid=kb;EN-US;q178893

(and if I cannot get WM_CLOSE to behave, I will end up testing what
are the real ill effects of TerminateProcess with WindowsXP...)



		Eero