Nate Lowrie wrote: > On 7/16/07, Bill Witherspoon <[EMAIL PROTECTED]> wrote: >>> Create the form as a dDialog. Show the form as a modal form. When >>> the user clicks ok or cancel, the form is not destroyed, it merely >>> hides itself. You are then free to call a method from the dialog >>> class you created (call it getData or getValue or whatever) and that >>> function will return your selected value. Then destroy the dialog and >>> you are done. >>> >>> This is simple compared to 2 completely unrelated forms... >>> >> I didn't pursue the dDialog idea because I assumed that it was for >> simple Yes/No scenarios. I have bizobjs, etc. in my search form. >> >> Can I add bizobjs to a dDialog? Or do you mean that there's a way to >> instantiate my sub-form as a dialog? I did see that you can specify >> "Modal", but I thought that was a non-starter with wxPython not >> supporting modal forms. >> >> Or have I completely missed your point? :-) > > Dialogs can range from the simple builtin ones dabo has to retrieve an > int or a string or display a message to some that are as massive and > complex as main forms. In fact, when you set a dForm's property to be > modal it actually instantiates a dDialog. Just make sure to pass the > property in the constructor or it won't work. > > You can add bizobjs to a dDialog just like a normal form. Check out > the dOkCancelDialog as it will automatically add the ok/cancel > controls for you. > > I will make a note to include the construction of a complex dialog in > the book example I am working on... > >> Bill. >> >>
Book? Drooool. I have to say a book would be very useful to me at this point in time. Thanks for the help on the above. Bill. _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
