Jump to content
  • Advertisement
Sign in to follow this  
Wavarian

WM_NCDESTROY: Deinitialization

This topic is 4876 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Just a quick question, when processing this message (before handing it over to DefWindowProc()), can I safely assume that all child windows still "exist" (but are not visible)? I'm talking about buttons, textboxes and the like. Cheers guys

Share this post


Link to post
Share on other sites
Advertisement
No, by WM_NCDESTROY all child windows are gone, whether
or not you call DestroyWindow(child). Right after WM_DESTROY,
even if you do not call DefWindowProc, Windows destroys all
child windows (unless you destroyed them yourself). Try some
test code in your message proc and see for yourself that no
matter what you do, the destruction order is:

Parent WM_DESTROY
Child WM_DESTROY
Child WM_NCDESTROY (child is officially gone)
Parent WM_NCDESTROY (parent is officially gone)

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

Participate in the game development conversation and more when you create an account on GameDev.net!

Sign me up!