PUI: Difference between revisions

Jump to navigation Jump to search
15 bytes added ,  31 December 2015
no edit summary
No edit summary
No edit summary
Line 6: Line 6:
[[File:menubar2.jpg|517px]]
[[File:menubar2.jpg|517px]]


PUI dialogs are standard [[PropertyList XML File]]s that are stored in $FG_ROOT/gui/dialogs, they can contain the widgets mentioned in {{readme file|gui}}, using a simple layout engine discussed in {{readme file|layout}}, and bindings using a combination of so called fgcommands (see {{readme file|commands}}) and custom [[Nasal]] code. In addition, each PUI/XML dialog may contain Nasal sections that are executed when opening/closing the dialog, a feature which is commonly used for procedurally creating/updating widgets using the cmdarg() API, which allows the dialog tree to be traversed and manipulated prior to the dialog being rendered.
In FlightGear, PUI dialogs are standard [[PropertyList XML File]]s that are stored in $FG_ROOT/gui/dialogs, they can contain the widgets mentioned in {{readme file|gui}}, using a simple layout engine discussed in {{readme file|layout}}, and bindings using a combination of so called fgcommands (see {{readme file|commands}}) and custom [[Nasal]] code. In addition, each PUI/XML dialog may contain Nasal sections that are executed when opening/closing the dialog, a feature which is commonly used for procedurally creating/updating widgets using the cmdarg() API, which allows the dialog tree to be traversed and manipulated prior to the dialog being rendered.


PUI/XML dialogs can be loaded, updated and closed using a handful of fgcommands:
PUI/XML dialogs can be loaded, updated and closed using a handful of fgcommands:

Navigation menu