The information in this article applies to:
SUMMARYAn application can terminate while in a message loop that is different from the primary GetMessage() loop. If this secondary message loop retrieves the WM_QUIT message from the message queue, the message must be reposted so that the primary GetMessage() loop can exit. MORE INFORMATION
An application can get into a secondary message loop that is different
from the primary GetMessage() loop in order to track drag messages,
yield periodically during lengthy processing, and so on. The user may
be able to terminate the application while the secondary message loop
is being used to retrieve messages from the message queue.
The primary message loop will not exit if the secondary message loop
does not repost the WM_QUIT message. Consequently, the application
will remain in memory even though all its windows are destroyed.
An alternative solution is to prevent the user from terminating the application while the application is in the secondary message loop. Additional query words: 3.00 3.10 close
Keywords : kb16bitonly kbSDKPlatform kbGrpUser kbWndw kbWndwMsg |
Last Reviewed: June 10, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |