I just don't understand... Some windows are closed after processing
of WM_CLOSE, others receive WM_DESTROY, yet others are destroyed
on WM_COMMAND messages. I have desperately been trying to implement
a notebook window class in C++. The window procedure that receives
the WM_xxx messages is a static C function which then calls the window
procedure associated with the specific C++ class. I want the static
function to call the C++ destructor if the "autoDestroy"-flag of that
class instance is set. To accomplish this I need a reliable way to
recognize when a window is destroyed.

"Normal" windows seem to receive WM_CLOSE or WM_DESTROY immediately
before they are actually destroyed. Dialog windows are closed when
they receive WM_COMMAND (unless a user-defined procedure returns
(MRESULT) FALSE on receipt of this message). But my notebook, which
consists of a frame window, client and WC_NOTEBOOK window, receives
additional messages (WM_FOCUSCHANGE, ...) _after_ WM_CLOSE.

Who can help?

Steffen

--- FastEcho 1.40+