Howto:Creating a Canvas GUI dialog file

From FlightGear wiki
Jump to navigation Jump to search
This article is a stub. You can help the wiki by expanding it.
Screen shot showing a simple Canvas GUI dialog with a handful of Button Widgets arranged with a vertical/vbox layout.

Targeted FlightGear versions: >= 3.20

First of all, we're going to add a new menu item to open our new dialog. This involves adding a new translation entry, as well as the actual menubar entry itself.

Editing Translations/en/menu.xml


Navigate to the sub-menu where you'd like to add your new dialog, e.g. "Equipment" in this case, and then add a key:

<canvas-demo-dialog>Canvas Demo Dialog</canvas-demo-dialog>

Editing gui/menubar.xml

Next, open fgdata/gui/menubar.xml and navigate to the corresponding sub-menu and add a new item/binding to load your dialog:


Creating the actual dialog file

Next, navigate to fgdata/Nasal/canvas/gui/dialogs and open/create $FG_ROOT/Nasal/canvas/gui/dialogs/CanvasDemo.nas to add some boilerplate code (this should match the basename of the dialog loaded in menubar.xml):

var DemoDialog = {
  new: func(width=140,height=160)
    var m = {
      parents: [DemoDialog],
      _dlg:[width, height], "dialog")
                         .set("title", "VBoxLayout")
                         .set("resize", 1),

    m._root = m._dlg.getCanvas().createGroup();
    var vbox =;

    # this is where you can add widgets from $FG_ROOT/Nasal/canvas/gui/widgets, e.g.:
    for(var i = 0; i < 5; i += 1 )
      vbox.addItem(,, {})
                                 .setText("Button #" ~ i)

    var hint = vbox.sizeHint();
    hint[0] = math.max(width, hint[0]);

    return m;

var demo =;

Finally, start FlightGear and open your new dialog

For a more sophisticated example, refer to Howto:Reset/re-init Troubleshooting.

Adding Widgets

1rightarrow.png See Howto:Creating a Canvas GUI Widget for the main article about this subject.

In order to keep your dialog sufficiently generic, you'll want to refrain from adding too much custom functionality to it, and instead decompose your functionality into a collection of widgets. Widgets are GUI controls like a label, button, checkbox etc that support styling - i.e. these widgets have a certain appearance and may respond to events such as being clicked for example. Whenever you create custom widgets instead of adding all the code to a single dialog, you'll end up with reusable components that can be easily other in other dialogs. In addition, you are making sure to establish a losely-coupled design, so that your widgets are sufficient generic and do not contain any use-case specific logic (think widgets being too specific to the dialog they were originally implemented for).

This means for example that a generic PropertyBrowser widget could be easily reused in other dialogs/windows requiring a corresponding property browser. But this also meanns that such a property browser widget should also be modularized, i.e. by using a lower-level ListView or TreeView widget and merely parameterizing that by showing properties. This approach has the added advantage that the corresponding ListView/TreeView widgets could be re-used in other places, such as for example an aircraft list, a Nasal Namespace Browser.

Likewise, a widget-focused approach means that useful functionality like an Interactive Nasal REPL can be easily used in other places, without developers having to do any refactoring.

We're also trying to make sure that Canvas Widgets can be easily used not just by GUI dialogs but also by Canvas-based instruments/MFDs - without any code duplication or Copy&Paste being required.

Creating MFD Dialogs

Sometimes you may have the need to present a GUI dialog for dealing with a MFD, potentially even showing the MFD screen itself in the GUI dialog. With Canvas, this can be accomplished by creating a dialog procedurally and adding a placement for the MFD (Canvas) that is to be shown, or even by showing an indepenent instance for your MFD (FGCanvas).

# helper function for registering events  (callbacks) with buttons (wrapped in a closure)
var createButton = func(root, label, clickAction) {
var button =,, {} )
button.listen("clicked", clickAction );
return button;
var (width,height) = (800,250);
var title = 'DPS Keypad';
# create a new window, dimensions are WIDTH x HEIGHT, using the dialog decoration (i.e. titlebar)
var window =[width,height],"dialog").set('title',title);
# adding a canvas to the new window and setting up background colors/transparency
var myCanvas = window.createCanvas().set("background","bg_color"));
# creating the top-level/root group which will contain all other elements/group
var root = myCanvas.createGroup();
# create a new layout for the keypad:
var myHBox =;
# assign the layout to the Canvas
var keypad =;

var mfd =,, {} )
	# this could also be another Canvas:

# list of all buttons we want to set up
var Buttons=[
'I/O RST',
## button setup using 4 vertical boxes added to a single hbox
foreach(var col; Buttons) {
	# set up a new vertical box
	var vbox =;
	# add it to the top-level hbox
	foreach(var btn; col) {
		(func() {
		var action=btn;
		var vbox=vbox;	
		var button=createButton(root:root, label: btn, clickAction:func {print("button clicked:",action);});
		# add the button to the vbox
	})(); # invoke anonymous function (closure)

Using Layouts

Note  This section still needs to be written (volunteers invivted to help!)-In the meantime, please refer to $FG_ROOT/Nasal/canvas/gui/dialogs/AircraftCenter.nas

Using Styling

Note  This section still needs to be written (volunteers invivted to help!)-In the meantime, please refer to $FG_ROOT/Nasal/canvas/gui/styles/DefaultStyle.nas