Destroying a sibling window in WM_DESTROY handler yields to strange behaviour
I have a native Windows program that uses the Windows SDK. The program uses several child windows in a frame. When the frame is destroyed with DestroyWindow, WM_DESTROY messages are sent to the child windows.