Order of cleanup

Ok, as far as I know, cleanup is mostly done in this order:
1) WM_CLOSE calls DestroyWindow()
2) WM_DESTROY calls PostQuitMessage()
3) Loop ends on WM_QUIT, and application returns

But is there any problem if it's done in this order:
1) WM_CLOSE calls PostQuitMessage()
2) Loop ends on WM_QUIT
3) DestroyWindow() is called after the loop
4) application returns

Will there be any problems with leftover messages or anything of the sort? And would there be problems with other arrangements similar to this?

>>2) Loop ends on WM_QUIT
3) DestroyWindow() is called after the loop<<

If the msg loop is stopped how will you get the DestroyWindow msg?

Hmm, ok. Because in one of my previous programs I needed to call the cleanup function of my graphics wrapper before calling DestroyWindow(), otherwise it would crash. Does this mean that I'll have to put all of my cleanup before the message loop ends (i.e. call a cleanup function which does de-initializing and stuff and then calls DestroyWindow())? And also, how would I signal my program to quit? Currently I just use PostQuitMessage() when I want to quit. Should I be calling a cleanup function>DestroyWindow>WM_DESTROY>PostQuitMessage( ) instead? :confused:

Quote:

---

Should I be calling a cleanup function>DestroyWindow>WM_DESTROY>PostQuitMessage( ) instead?

---

Yes, that should work.

How about running your debugger to see? :)

Ok, thanks. But how would running a debugger help?