20,741
edits
Talk:Aircraft checklists: Difference between revisions
Jump to navigation
Jump to search
→Checklists & Autostart + limits.nas: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40005.html
(http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39799.html) |
(→Checklists & Autostart + limits.nas: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40005.html) |
||
| Line 8: | Line 8: | ||
: Ah, that's a much more contentious one. The problem, from my point of view, is that our -set.xml files only encode one aircraft state (usually cold-and-dark). To encode (accurately) engines-running or in-flight as the start state, needs some kind of profile system where properties can have different values, and XML / Nasal can be initialised differently. That would make nice in-air starts possible (gear already up, throttles at sane position), as well as offering 'cold, dark and parked' or 'on the active and ready to go' as options. (And end all the per-aircraft 'auto-start' menu options - since they'd become standardised). <ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39672.html |title= Crazy usability suggestion of the day|author=James Turner |date= Tue, 05 Mar 2013 03:39:23 -0800}}</ref>|James Turner}} | : Ah, that's a much more contentious one. The problem, from my point of view, is that our -set.xml files only encode one aircraft state (usually cold-and-dark). To encode (accurately) engines-running or in-flight as the start state, needs some kind of profile system where properties can have different values, and XML / Nasal can be initialised differently. That would make nice in-air starts possible (gear already up, throttles at sane position), as well as offering 'cold, dark and parked' or 'on the active and ready to go' as options. (And end all the per-aircraft 'auto-start' menu options - since they'd become standardised). <ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39672.html |title= Crazy usability suggestion of the day|author=James Turner |date= Tue, 05 Mar 2013 03:39:23 -0800}}</ref>|James Turner}} | ||
{{cquote| | |||
:: I'm planning to extend this function (bindings support) 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.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40005.html |title= Further enhancement to checklists - binding support|author=Stuart Buchanan |date= Wed, 01 May 2013 14:54:56 -0700}}</ref>|Stuart Buchanan}} | |||
== Supporting Startup Situations == | == Supporting Startup Situations == | ||