20,741
edits
mNo edit summary |
No edit summary |
||
Line 21: | Line 21: | ||
sane way to migrate to this split without lots of breakage and frustration. Any | sane way to migrate to this split without lots of breakage and frustration. Any | ||
ideas welcome.</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40838.html|title=<nowiki></nowiki>|author=<nowiki></nowiki>|date=<nowiki></nowiki>}}</ref>|<nowiki></nowiki>}} | ideas welcome.</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40838.html|title=<nowiki></nowiki>|author=<nowiki></nowiki>|date=<nowiki></nowiki>}}</ref>|<nowiki></nowiki>}} | ||
{{cquote|<nowiki>the problem is the OSs have already decreed that Ctrl (Command on Mac) is | |||
the standard shortcut key, so lots of Ctrl-something have standard meanings | |||
which FlightGear deviates from. Though we escape the worst of it since we don't | |||
support file or edit operations. | |||
Keep in mind if the GUI things such as dialogs were moved to Ctrl-blah, that | |||
frees up lots of normal keys for use, which are currently taken up by simulator | |||
things. While I agree Ctrl is probably the easiest modifier to access (except | |||
maybe shift, since there's two, so it's more friendly for left-handed people), | |||
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>}} | |||
<references/> | <references/> |