Hi Smasher/Devourer'
Quote Originally Posted by Smasher/Devourer
I wrote that code to be a WinAPI analogue of what you get when you create a dialog-based application with the MFC AppWizard. In other words, the box created from IDD_MAINDIALOG is assumed to be the application's main window. Under that specific set of circumstances, where the dialog's parent window is always set to NULL, does it matter whether the dialog is modal or modeless?
Yes, in API based application it maters. In MFC application CWinApp provides proper handling of MFC modeless dialog, while message loop in Win32 application generated by app wizard does not.
Anyway, MFC dialogs ara always created as modeless. Modal state is achieved by disabling application main window and establishing dialog’s local message loop.
Quote Originally Posted by Smasher/Devourer
My Windows programming experience is admittedly quite limited, so it could be that I'm missing something obvious here.
Underestimating yourself? I think your posts are pretty good.
Quote Originally Posted by Smasher/Devourer
But I'm not sure why you'd want to create a modeless dialog in this situation.
Quote Originally Posted by beecheyp
sample Win32 project based on a dialog application.
If it were "Win32 application project based on a dialog", it would have been clearer. I just thought that modeless dialog as main window, or modeless dialog in SDI or MDI –like QIN32 application falls into above requirement.
Your point is well taken; I thought that mentioning modeless dialog would supplement your post.