🚀 go-pugleaf

Frank Gruber wrote:

> It is getting even better. As shutdown is difficult to debug I put a fopen,
> sprintf, fclose
> sequence after every action I perform in the event handler to find out where
> the
> handler is getting interrupted. With these lines inside the message handler
> it is no longer
> interrupted by Windows. If I remove these lines the problem comes back.
> IMHO the whole Windows shutdown process was allways full of quirks, badly
> designed
> or at least badly dokumented. Just my 2 cents.

You just need to read MSDN. In some topic (don't have MSDN now) there's 
a statement saying something like this: "After this message is sent, any 
API operation can fail with ERROR_SHUTDOWN_IN_PROGRESS error". And this 
is what happens. Actually, you can't trust OS even after 
WM_QUERYENDSESSION. So all shutdown actions you want to do should be 
done in responce to WM_QUERYENDSESSION. The best thing is to close the 
application by posting WM_CLOSE to main form when you receive 
WM_QUERYENDSESSION and not wait until system kills your application. In 
ElPack (http://www.eldos.org/elpack/elpack.html) we have a special unit, 
whose only job is to track WM_QUERYENDSESSION and gracefully close the 
application. This unit is also present in my article on Delphi3000.

-- 
Eugene Mayevski
Flexible cross-platform information exchange framework
http://www.msgconnect.com/