20,741
edits
Keyboard function priority list: Difference between revisions
Jump to navigation
Jump to search
m
Keyboard function priority list (view source)
Revision as of 14:06, 29 September 2013
, 29 September 2013no edit summary
m (Template:Key press) |
mNo edit summary |
||
| Line 10: | Line 10: | ||
What I'd like to see is the entire 'Ctrl' (Command on Mac) space reserved for GUI functions, like a normal application - Ctrl-Q for quit, Ctrl-M for map dialog, Ctrl-A for autopilot dialog, Ctrl-R for replay dialog (or radios dialog :) - then have a complete discussion about which key-bindings make sense on | What I'd like to see is the entire 'Ctrl' (Command on Mac) space reserved for GUI functions, like a normal application - Ctrl-Q for quit, Ctrl-M for map dialog, Ctrl-A for autopilot dialog, Ctrl-R for replay dialog (or radios dialog :) - then have a complete discussion about which key-bindings make sense on | ||
the main keyboard. This is basically a usability discussion, so everyone will have strong opinions :)<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39648.html |title= Keyboard bindings|author=James Turner |date= Sun, 03 Mar 2013}}</ref>|James Turner}} | the main keyboard. This is basically a usability discussion, so everyone will have strong opinions :)<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39648.html |title= Keyboard bindings|author=James Turner |date= Sun, 03 Mar 2013}}</ref>|James Turner}} | ||
{{cquote|<nowiki>A separate step, much harder to make happen, would be to explicitly reserve the | |||
Ctrl (Command on Mac) keybinding space for menu/non-aircraft keyboard | |||
shortcuts. I would really like to do this so we can have user-friendly | |||
key-bindings for dialogs and standard items, such as Ctrl-Q to quit, Ctrl-A for | |||
autopilot dialog, Ctrl-P for pause, Ctrl-R for reply, etc. [And the entire | |||
normal key / key + shift / key+alt ranges available FOR aircraft functions, of | |||
course) The problem is right now we have aircraft using Ctrl- shortcuts for | |||
many things (usually because they're the only choice), and I can't decide a | |||
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>}} | |||
<references/> | <references/> | ||