Howto:Canvas dialog examples: Difference between revisions

At the moment it has 1:

* [[Extra EA-500/failure dialog|Extra500 Failure Dialog]]

== Extra500 failure dialog ==

# Initiate the listeners to make certain elements interactive

* Making the listeners and linking them to canvas/.svg elements (howto make clicking on it make it do something)   

=== Namespace and Menu entry ===

The dialog is set-up like a normal nasal namespace in the  -set file:

     <Dialogs>

       <file>Aircraft/extra500/Dialogs/failuredialog.nas</file>

     </Dialogs>

And called (opened) though a menu entry in /Dialogs/extra500-menu.xml just like any other classical menu entry.

   <name>Failure-dialog</name>

   <label>Failure Dialog</label>

       ]]></script>

   </binding>

This means there needs to be a loaded Class called "Failuredialog" in the namespace "Dialogs" with an internal function called "openDialog".

With the last line of code above, we invoke the following:

   var m = {parents:[FailureClass]};

   m._title = 'Extra500 Failure Dialog';

   return m;

  },

So we make the Class, set a title, make a canvas and even set a timer.

This happens when the GEAR tab in the menu is pressed. The menu is re-setted and then the gear tab is changed color to indicate it is selected.

All the other pages are hidden, the gear page is show and finally all gear-buttons are updated. The status of the buttons depends on fg-properties. They have no listeners, but are only updated when the page is show. This is a bit easier and saves a lot of listeners. The disadvantage is that the buttons (they change color when a pressed and a failure is initiated) are not updated automatically. Maybe not ideal for a 'front end'...