There must be a workaround for this problem. The Crownwood Consulting “Magic” library has a MenuControl class derived from ContainerControl, which works correctly in an MDI interface. As far as I can see, it simply finds the MdiClient child control, subclasses that window and prevents the WM_MDISETMENU and WM_MDIREFRESHMENU messages from being sent to it.
In my opinion, the lack of MDI support is the biggest problem for the SmartUI components at the moment. I have been able to create a tabbed-MDI application with the SmartMenu, but it involves a lot more work than a standard MDI application.
Imported from legacy forums. Posted by Richard (had 543 views)