20,741
edits
No edit summary |
No edit summary |
||
Line 33: | Line 33: | ||
I think by this logic a shortcut with *no* modifiers is even easier to access, | I think by this logic a shortcut with *no* modifiers is even easier to access, | ||
and that's an argument in *favour* of such change :)</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40853.html|title=<nowiki></nowiki>|author=<nowiki></nowiki>|date=<nowiki></nowiki>}}</ref>|<nowiki></nowiki>}} | and that's an argument in *favour* of such change :)</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40853.html|title=<nowiki></nowiki>|author=<nowiki></nowiki>|date=<nowiki></nowiki>}}</ref>|<nowiki></nowiki>}} | ||
{{cquote|<nowiki>this actually shows a larger problem. Obviously it isn't too | |||
uncommon for aircraft to disable or override specific menu items - | |||
mainly affects menu items for the radio stack and autopilot. | |||
Unfortunately all of this is done using fixed menu item positions - | |||
e.g. 5th menu, 3rd item... So any change of the menu item ordering | |||
currently breaks lots of planes. And obviously the recent menubar | |||
overhaul has done just that. | |||
We'll need to adapt all the aircraft using such hacks to the changed | |||
menu structure. And might need to think about a better solution to | |||
avoid future problems of this kind.</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg30166.html|title=<nowiki></nowiki>|author=<nowiki></nowiki>|date=<nowiki></nowiki>}}</ref>|<nowiki></nowiki>}} | |||
<references/> | <references/> |