13,208
edits
Howto:Canvas dialog examples: Difference between revisions
Jump to navigation
Jump to search
m
cat: Canvas GUI
m (cat: Canvas GUI) |
|||
| (2 intermediate revisions by one other user not shown) | |||
| Line 2: | Line 2: | ||
At the moment it has 1: | At the moment it has 1: | ||
* [[Extra EA-500/failure dialog|Extra500 Failure Dialog]] | * [[Extra EA-500/failure dialog|Extra500 Failure Dialog]] | ||
[[File:Extra500-Failuredialog-fuel.png|500px|right|Extra 500 - failure dialog - Fuel]] | |||
== Extra500 failure dialog == | == Extra500 failure dialog == | ||
| Line 19: | Line 21: | ||
# Initiate the listeners to make certain elements interactive | # 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) | * Making the listeners and linking them to canvas/.svg elements (howto make clicking on it make it do something) | ||
=== Namespace and Menu entry === | === Namespace and Menu entry === | ||
| Line 66: | Line 67: | ||
With the last line of code above, we invoke the following: | With the last line of code above, we invoke the following: | ||
<syntaxhighlight lang="javascript"> | |||
new : func(){ | |||
var m = {parents:[FailureClass]}; | var m = {parents:[FailureClass]}; | ||
m._title = 'Extra500 Failure Dialog'; | m._title = 'Extra500 Failure Dialog'; | ||
| Line 74: | Line 76: | ||
return m; | return m; | ||
}, | }, | ||
</syntaxhighlight> | |||
So we make the Class, set a title, make a canvas and even set a timer. | So we make the Class, set a title, make a canvas and even set a timer. | ||
| Line 176: | Line 179: | ||
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. | 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'... | 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'... | ||
[[Category:Canvas GUI]] | |||