"johnf" <[EMAIL PROTECTED]> wrote > 1 and 3 are my reasons. I'm creating a Dabo app. When I attempted > to create > a special class that contained a dialog box I discovered that the > dialog > class created an indepentant type of window and allowed my program > to > continue running without waiting for the dialog to return a value > first.
Are you sure you made it a modal dialog? Any dialog will do that if it is opened modelessly, you need to use the modal version to make it block the app. Putting the class code in a functiion is legal but very inefficient and also prevents you from storing state etc in the dialog - you would need to reinitialise all valuues on each use. Thats OK if its simple but a lot of work(and slow) if its complex. HTH, -- Alan Gauld Author of the Learn to Program web site http://www.freenetpages.co.uk/hp/alan.gauld _______________________________________________ Tutor maillist - Tutor@python.org http://mail.python.org/mailman/listinfo/tutor