🚀 go-pugleaf

"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:45f0a594@newsgroups.borland.com...
>
> "Dennis Jones" <nospam@nospam.com> wrote in message
> news:45f095bf$1@newsgroups.borland.com...
>
>> Have you considered that it might not be YOUR application that is
>> preventing Windows from shutting down?  You said that your "fake"
>> shutdown app is getting back the correct result.  That would seem to
>> indicate that even if there were other components in the mix using
>> AllocateHWnd, that they are not affecting the application's ability
> to
>> notify Windows that it is okay to shutdown.
>
> The other thing to take into account is that the test app which is
> sending the fake shutdown is sending the messages to only one window.
> If there are multiple top-level windows in the program being tested,
> such as due to AllocateHWnd() calls, then the shutdown messages need
> to be sent to each individual window, each window being tested
> separately from the other windows.  Any one of them could be reporting
> an unacceptable shutdown.

Yeah, I just realized that a minute ago.  The OP wasn't far off in asking 
about debugging the messages.  Perhaps a windows message spy program 
(http://www.catch22.net/software/winspy.asp) would be useful.  I've used 
programs like this in the past, but it has been a long time, so I have no 
idea which ones, if any, are any good.

- Dennis