On 5/21/10 8:42 AM, Ed Leafe wrote: > On May 21, 2010, at 11:28 AM, John wrote: > >> My point is simple - it's not all that easy to create an MDI app with the >> Dabo >> tools. > > That's correct: MDI is not supported in the Class Designer because a) I > never use it and b) no one mentioned it until now.
Oh, I just discovered that dFormMain isn't included in the possible form classes. Ed, could that be added simply enough? Then we could later on maybe even have a MDI helper page on the "save runnable app" dialog. Something like this that shows up when the form we are saving as a runnable app is a dFormMain instance: <FixedWidthFontAlert> +======================+ | MDI Settings | +----------------------+ |We suggest MDI on Win | |and Mac, but not Lin. | |Make app MDI on: | | [x] Win | | [x] Mac | | [ ] Lin | +======================+ </FixedWidthFontAlert> Or maybe we don't want to expose dFormMain at all. But when 'save runnable app' is invoked, make a dFormMain in the background automatically, if MDI is chosen. dFormMain doesn't need anything tweaked by the appdev except for status bar updates, menu bar, and tool bar. I'm just kind of brainstorming here, so feel free to tear the idea to shreds. MDI is actually the best mode to run on Mac, IMO, since it leads to a more native feel. The existence in the background (non-visible to the user) of the main form is kind of hokey, though, but still workable. And I still prefer MDI on Windows, and suspect a lot of people besides me do, too. Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
