Updated: March 31, 2006 for release 0.8.2

Dialogs are defined in dialog.py. They are all modal and map directly to a wxPython class, which map to an underlying OS dialog where available. The one exception is the findDialog which I coded from scratch. In PythonCard, dialog use has been simplified by wrapping the underlying classes with a function, so that a modal dialog call only requires a single line of code. The result of a dialog call is always a dictionary.

alertDialog           (variation of wx.MessageDialog)
colorDialog           (wx.ColourDialog)
directoryDialog       (wx.DirDialog)
fileDialog            (wx.FileDialog)
fontDialog            (wx.FontDialog)
messageDialog         (wx.MessageDialog)
multipleChoiceDialog  (wx.lib.dialogs.MultipleChoiceDialog)
scrolledMessageDialog (wx.lib.dialogs.ScrolledMessageDialog)
singleChoiceDialog    (wx.SingleChoiceDialog)
textEntryDialog       (wx.TextEntryDialog)

Creating and Interacting with Common Dialogs in PythonCard describes the use of each of the dialogs above.

Some options are specified via constants, see dialog.py for a full list as well as the dialogs sample which shows the various dialogs in use.

The CustomDialog class allows you to define custom modal dialogs using the same components and layout mechanisms and event handlers as used for backgrounds. See the dbBrowser, dialogs, resourceEditor, textEditor, and textRouter samples for examples of custom modal dialogs. The CustomDialog class is defined in model.py.

There are no modeless dialogs and discussions I've had with Rowland about this topic concluded that there is not much point to the term 'modeless dialog' since in PythonCard there wouldn't be much difference from a regular background.

| General Concepts and Limitations | Components | Dialogs | Events and Handlers | Menus | Resource Files | Runtime Tools

SourceForge Logo Valid XHTML 1.0! Valid CSS!

$Revision: 1.4 $ : $Author: alextweedly $ : Last updated $Date: 2006/04/06 11:00:26 $