WM_CLOSE is already handled by the default window procedure, DefWindowProcW, which calls DestroyWindow. It's only necessary to override the default for WM_CLOSE if you want to prevent the window from being destroyed.
Vincent Povirk
On Thu, Aug 21, 2008 at 10:44 PM, James McKenzie jjmckenzie51@earthlink.net wrote:
Vincent Povirk wrote:
Why doesn't the WM_DESTROY case handle this properly? At first glance, it appears to have code for stopping the running applets and quitting from the main loop.
WM_CLOSE is different than WM_DESTROY. This is a missing case that needs to be handled whenever the Windows Manger receives this message. Good catch, Steven.
James McKenzie