wxWidgets not playing nicely with MFC
-
Hi , I have an MFC application whixh is huge already , and I have recently switched to writing new Dialogs using wxWidgets, but this causes unexpected behaviour, if I simlpy create wxWidgets dialogs from the MFC classes, then the program runs fine, but I get multiple icons for the application on the TaskBar, and , if I create the wxDialog as a child of the MFC app - using ::SetParent(...) , then the wxDialog is "locked" onto the main apps client area as if it were a child control, I have tried many things to get this working, even using AssociateHandle(HWND...) to Associate my main app's handle with a wxWindow and trying to ReParent(...) using that as the parent for this wxDialog, all to no avail. If anybody has any clue whatsoever as to how to get around this strange wxWidgets behaviour, then your help would be appreciated beyond measure. Thank you Max PS: Seasons Greetings :-O
The tears shed in vain and the hatred and pain will be nothing but dust at the end of the day
-
Hi , I have an MFC application whixh is huge already , and I have recently switched to writing new Dialogs using wxWidgets, but this causes unexpected behaviour, if I simlpy create wxWidgets dialogs from the MFC classes, then the program runs fine, but I get multiple icons for the application on the TaskBar, and , if I create the wxDialog as a child of the MFC app - using ::SetParent(...) , then the wxDialog is "locked" onto the main apps client area as if it were a child control, I have tried many things to get this working, even using AssociateHandle(HWND...) to Associate my main app's handle with a wxWindow and trying to ReParent(...) using that as the parent for this wxDialog, all to no avail. If anybody has any clue whatsoever as to how to get around this strange wxWidgets behaviour, then your help would be appreciated beyond measure. Thank you Max PS: Seasons Greetings :-O
The tears shed in vain and the hatred and pain will be nothing but dust at the end of the day
Is NOBODY going to even try to help me out on this one??? Well , anyways , I have found a workaround for the strange behaviour which causes more than one icon to show up in the taskbar, I'll be writing an article soon once I've gotten standard behaviour from my code. Come on guys , where's your Christmas spirit?
The tears shed in vain and the hatred and pain will be nothing but dust at the end of the day
-
Is NOBODY going to even try to help me out on this one??? Well , anyways , I have found a workaround for the strange behaviour which causes more than one icon to show up in the taskbar, I'll be writing an article soon once I've gotten standard behaviour from my code. Come on guys , where's your Christmas spirit?
The tears shed in vain and the hatred and pain will be nothing but dust at the end of the day
Max_Power_Up wrote:
Come on guys , where's your Christmas spirit?
My guess is that a) lots of folks aren't online over the holiday break, and b) most folks who use wxWidgets (like myself :)) don't usually have both MFC and wx in the same exe and, as such, can't answer your question. Judy
-
Max_Power_Up wrote:
Come on guys , where's your Christmas spirit?
My guess is that a) lots of folks aren't online over the holiday break, and b) most folks who use wxWidgets (like myself :)) don't usually have both MFC and wx in the same exe and, as such, can't answer your question. Judy
Thanks JudyL_FL, I have found that it is necessary to reparent the wxWidgets window to the top-level MFC dialog, this causes wxWidgets to share taskbar resources with the MFC app.
The tears shed in vain and the hatred and pain will be nothing but dust at the end of the day Hit me on my blog!