Ed Leafe wrote: > On Jul 6, 2008, at 12:51 AM, Paul McNett wrote: > >> Oh, okay. I thought the Parent would be the control that needed the >> dialog, not the form. And so the dialog would be instantiated once per >> control, not once per form. > > > That was my first approach, too, but it resulted in too much hassle > coordinating the various dialogs that could result. Then it hit me > that there would never be more than one showing at a time (they're > modal, after all), so it made sense to have it controlled centrally by > the form.
The benefit to the other way is that, once created, this-or-that calendar control (for example) wouldn't need its controls added again once it has been instantiated once. IOW, The form is created, with a number of widgets that will use a floating dialog. None of the floating dialogs are instantiated yet. The user clicks to expand a calendar on one of the controls, so the floating dialog is created, populated, and shown. When the user presses Esc to cancel or Tab/Enter to accept, the dialog is hidden but not destroyed. The next time this dialog is shown, all we need to do is show() and setFocus() to the first control on the dialog. Just ideas. 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]
