20,741
edits
Aircraft checklists: Difference between revisions
Jump to navigation
Jump to search
m
http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40005.html
(Add <binding> documentation) |
m (http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40005.html) |
||
| Line 65: | Line 65: | ||
See the [[Cessna 172P]] for an example of how this all fits together. | See the [[Cessna 172P]] for an example of how this all fits together. | ||
== Bindings Support == | |||
Aircraft authors may now add one or more <binding> elements to a checklist <item>. Conceptually, these are the actions that the user should execute | |||
to complete the item. The checklist GUI displays items with such <binding> elements with an additional [>] button. Clicking on the button executes the | |||
bindings, allowing the user to watch as the computer/co-pilot/instructor executes the checklist item. | |||
The <binding> element is exactly as you would expect - so property-assign, nasal etc. works. | |||
Due to the power of Nasal and properties, this feature only required 13 lines of code to write, most of which is displaying the button! | |||
I'm planning to extend this function so that checklists with one or more items containing a <binding> element can have an (optional) button | |||
to execute the entire checklist. I'm still thinking of how best to implement this, as I think one would want a gap between each item. | |||
I'd highlight the property-interpolate command which provides a very convenient way to interpolate a property to a new value. See | |||
Docs/README.commands if (like me) you were unaware of this :). | |||
I've updated the c172p checklists to use this feature, including some rather cute interpolations of the throttle, mixture and trim controls. | |||
==Reloading Checklists== | ==Reloading Checklists== | ||