Changes

Jump to navigation Jump to search
237 bytes added ,  14:33, 29 December 2017
Line 51: Line 51:  
If that is something that is considered too fragile or problematic for other reasons (work load caused ...), we could just as well use/support conditions (properties) in the menubar and allow aircraft to explicitly opt in/out as needed, even if just by setting a few properties using a dedicated "mode" property.<ref>https://forum.flightgear.org/viewtopic.php?f=6&t=33110&p=320574&hilit=modes+startup#p320574</ref>
 
If that is something that is considered too fragile or problematic for other reasons (work load caused ...), we could just as well use/support conditions (properties) in the menubar and allow aircraft to explicitly opt in/out as needed, even if just by setting a few properties using a dedicated "mode" property.<ref>https://forum.flightgear.org/viewtopic.php?f=6&t=33110&p=320574&hilit=modes+startup#p320574</ref>
    +
 +
== Use Cases ==
 +
Supporting different startup "modes" that are session-specific provides a nice way to support different use-cases, while keeping them separate. For instance:
 +
 +
* flight-sim (default)
 +
* spaceflight
 +
* marine
 +
* RC
 +
* combat
    
== Implementation ==
 
== Implementation ==

Navigation menu