MFC dialog problem
-
Hi, I created a dialog with the mfc app creator, then created a non modal dialog from within that dialog class with the extended style WS_EX_APPWINDOW applied on the initdialog like hmmm... ModifyStyleEx(0, WS_EX_APPWINDOW); This gives me a taskbar space for the new non-modal window. BUT, when I minimize the main modal app dialog, it also minimizes the non-modal window. I tried catching the window messages to the non-modal with pretranslate message, but there is no message when it's minimized, or when it's restored. No WM_SIZE or nothing. It's almost like MFC magic. I'm guessing this is some kind of wierd undocumented message mapping we can't see in the source SRC files??? So, how do i stop MFC from taking control of non-modal dialogs with the main dialog window in a dialog based app? PS- I also tried setting the parent to null, but it did nothing. hey
-
Hi, I created a dialog with the mfc app creator, then created a non modal dialog from within that dialog class with the extended style WS_EX_APPWINDOW applied on the initdialog like hmmm... ModifyStyleEx(0, WS_EX_APPWINDOW); This gives me a taskbar space for the new non-modal window. BUT, when I minimize the main modal app dialog, it also minimizes the non-modal window. I tried catching the window messages to the non-modal with pretranslate message, but there is no message when it's minimized, or when it's restored. No WM_SIZE or nothing. It's almost like MFC magic. I'm guessing this is some kind of wierd undocumented message mapping we can't see in the source SRC files??? So, how do i stop MFC from taking control of non-modal dialogs with the main dialog window in a dialog based app? PS- I also tried setting the parent to null, but it did nothing. hey
alternatively, does anybody out there have a doc with the internal message mapping of MFC dialogs i could take a look at? I can't get why it doesn't so much as send a message to the 2nd dialog when it's magically minimized and the taskbar space is removed. It seems wrong. hey
-
Hi, I created a dialog with the mfc app creator, then created a non modal dialog from within that dialog class with the extended style WS_EX_APPWINDOW applied on the initdialog like hmmm... ModifyStyleEx(0, WS_EX_APPWINDOW); This gives me a taskbar space for the new non-modal window. BUT, when I minimize the main modal app dialog, it also minimizes the non-modal window. I tried catching the window messages to the non-modal with pretranslate message, but there is no message when it's minimized, or when it's restored. No WM_SIZE or nothing. It's almost like MFC magic. I'm guessing this is some kind of wierd undocumented message mapping we can't see in the source SRC files??? So, how do i stop MFC from taking control of non-modal dialogs with the main dialog window in a dialog based app? PS- I also tried setting the parent to null, but it did nothing. hey
-
Hi, I created a dialog with the mfc app creator, then created a non modal dialog from within that dialog class with the extended style WS_EX_APPWINDOW applied on the initdialog like hmmm... ModifyStyleEx(0, WS_EX_APPWINDOW); This gives me a taskbar space for the new non-modal window. BUT, when I minimize the main modal app dialog, it also minimizes the non-modal window. I tried catching the window messages to the non-modal with pretranslate message, but there is no message when it's minimized, or when it's restored. No WM_SIZE or nothing. It's almost like MFC magic. I'm guessing this is some kind of wierd undocumented message mapping we can't see in the source SRC files??? So, how do i stop MFC from taking control of non-modal dialogs with the main dialog window in a dialog based app? PS- I also tried setting the parent to null, but it did nothing. hey
Try settings the parent to the desktop window, this should fix it use GetDesktopWindow(); Ralph Varjabedian Software Engineer
-
Try settings the parent to the desktop window, this should fix it use GetDesktopWindow(); Ralph Varjabedian Software Engineer
ModifyStyleEx(0, WS_EX_APPWINDOW); SetParent(GetDesktopWindow()); Tried it this way in the non-modal initdialog. No Go Senior! Thanks for the suggestion, but I knew it wasn't going to work because i had previously tried setting it to NULL. The maindlg window of my dlg app is still minimizing it and removing the taskbar spot on minimization. And all the while sending No messages to the WndProc of the modeless dialog. I have a feeling that this is some powerful MFC voodoo that can only be resolved deep within the cavernous realms of the microsoft building. In other words unless somebody just knows, i don't know if it can be "figured out", since it's depriving any Wnd after the initial dialog of any type of messages about the altered window state hey