On Fri, Feb 15, 2013 at 9:23 PM, Alan Teeder wrote: > Is there any way to chain checklists automatically so that they follow one > another in a pre-defined order?
They should appear in the checklists dialog in the order in which they are defined in the XML file, so simply define them in the order you wish. > An alternative, which may have further advantages, would be to have a tree > structure of checklists, where one branch has to be completed before going > back to the trunk and then on to the next branch. Note that the checklist function doesn't enforce any action on the part of the pilot. It simply provides a convenient representation of a textual checklist plus some highlighting to indicate completed steps and (once I get around to it) the ability to highlight the relevant controls. > e.g. on cockpit entry I want to do a right to left sequence of checks, > starting with the port side panel, going on to the port coaming, then the > port instrument panel etc, covering the whole cockpit methodically. Each of > these panels has up to a dozen checks. This is how the checks were actually > organised (with a book of cards) on this particular aircraft. The cockpit > entry checks were then followed by the start sequence, the after starting, > the take off, after take-off, circuit ad approach /landing checks. I don't think that's a tree structure, just an ordered list, which is already provided. > The emergency checks also follow a tree structure, but in this case the next > branch depends upon the result of a particular check. (e.g. did the engine > relight within 20 seconds?) I think that's getting a bit specialized, and overly complicated. I'd also point out that we're just supporting the pilot's use of checklists, not attempting to automate them. I don't think it's unreasonable to have a checklist items that says "if the engine does not relight within 20 seconds, run the Engine Dead Checklist" (Additionally I'd be pleasantly surprised if our systems/failure modelling is good enough that such a decision tree wouldn't always go down the same path.) -Stuart ------------------------------------------------------------------------------ The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
