Changes

Jump to navigation Jump to search
205 bytes added ,  14:32, 29 December 2017
m
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>
    +
 +
== Implementation ==
 +
Startup modes would be stored in $FG_ROOT/Modes, using a custom set of PropertyList/XML overlays:
 +
 +
* defaults.xml (formerly, preferences.xml)
 +
* keyboard.xml
 +
* mouse.xml
 +
* menubar.xml
    
== References ==
 
== References ==
 
{{Appendix}}
 
{{Appendix}}

Navigation menu