-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 David Megginson schrieb: > [...] > 2. Decide on a block of keys to be set aside for per-aircraft key assignment. > [...]
Hi David, it's a great idea at the right time to set a standard for the key bindings. Here are some of my thoughts: 1) try to stay consistent to the most important bindings we've got so far - this helps our user base 2) offer an alternative setting for ex M$FS users :) 3) be consistent (if necessary break 1) for that) 4) use Ctrl and Alt to seperate the bindings. (This helps 3) and 1) as the key might stay the same, just an Ctrl or Alt is added) e.g.: key and shift-key are for default plane actions (shift-key is the opposite). Gear, flaps and lighting are great examples. Alt-key and Alt-shift-key are for plane model individual settings. Ctrl-key and Ctrl-shift-key are for simulator settings. (e.g. Ctrl-[t] could speed up the simulation and Ctrl-shift-[t] could slow it down) This set would be consistent. Default action is the key itself. The reverse action is by adding shift. The default plane actions are easy to reach and separated from the model specific options and the simulator options. CU, Christian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHOYjqoWM1JLkHou0RCNULAJ93G9TgkxpJOBLF5MuUi4BcrKcIEgCcCaDc ufrqpqxaRgpp4Pd6oRM/K5A= =grcB -----END PGP SIGNATURE----- ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
