ASM Community

Create several global handles (one for each of the dialogs) when you create the dialogs, save the handle value, when the dialog is closed set the handle to NULL. Then, when you go to create a dialog, ONLY create the dialog if the stored handles value is NULL. This will ensure that only one of each dialog can be open at a time.

Regards,
Bryant Keller

ALT+F4 Posts a "WM_CLOSE" to your window. DefWindowProc destroys the window upon encountering WM_CLOSE and sends WM_DESTROY. Just handle the WM_CLOSE yourself, so that the DefWindowProc won't destroy your window. Please bear in mind that your application can stil be terminated in many other ways. Also make sure that you make a 'bypass' to WM_CLOSE, so that you can terminate your app cleanly.

Like:
1. initialize 'testvar' to 0
2. while handling WM_CLOSE: if (testvar == 0) then return 0 else DefWindowProc
3. a menu item 'exit' (or whatever) sets the 'testvar' to 1 and sends WM_CLOSE.

This way you'll disable Alt+F4, while still being able to terminate (using a menu item, for example).


There's also an easier and better looking way:
Just put CS_NOCLOSE flag when registering the window's class. CS_NOCLOSE disables the 'X' button and prevents it from sending WM_CLOSE. This is the preferred way (The one above was just to explain you how the WM_CLOSE and WM_DESTROY messages work ;) ).