20,741
edits
Keyboard function priority list: Difference between revisions
Jump to navigation
Jump to search
m
add updates from devel list: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39648.html
No edit summary |
m (add updates from devel list: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39648.html) |
||
| Line 1: | Line 1: | ||
{{Template:RFC Navigation}} | {{Template:RFC Navigation}} | ||
{{cquote|My point of view is that the current keybindings file is a mess, with many historical bindings, and also it binds in the ASCII space, as opposed to the scan code space, so we can't distinguish keypad vs normal number keys, and various other combinations, even though osgViewer supports that. | |||
My *personal* feeling is that unless it's something the > 50% of users use *each flight*, it shouldn't be a keybinding. So flaps, trim, CDI/HSI heading, | |||
fine, but things to change view distance or FoV seem unnecessary to me. | |||
The other issue is the keybindings are effectively 'full' (we can't easily add more), because they've been added and added over the years, but rarely removed, so at this point every key 'does something', but often something quite obscure. | |||
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}} | |||
<references/> | |||
As a first step in the keyboard refactoring, we need to come up with a prioritized list of functions that (a) are general enough to apply to most (or at least many) aircraft, and (b) are important enough to justify a keyboard shortcut rather than just a menu/dialog or a model hotspot. | As a first step in the keyboard refactoring, we need to come up with a prioritized list of functions that (a) are general enough to apply to most (or at least many) aircraft, and (b) are important enough to justify a keyboard shortcut rather than just a menu/dialog or a model hotspot. | ||