> From: [EMAIL PROTECTED]
> [mailto:flightgear-devel-admin@;flightgear.org]On Behalf Of Curtis L.
> Olson
> So I would say go for it, people can always maintain their local
> overrides. It's not like we are changing any core functionality here.
>
> You will never get a consensus for anything you put before the list,
> but if you want to do anything really radical it might make sense to
> have a little discussion first.
>From a user's point of view, I am not against changing the default bindings,
but would propose making them at once (maybe after discussion where
required) and announcing all of them in a list. Given people are used to the
present bindings and given they are in the "cheat sheet" (not sure anyone's
using that...) I already see the posts like "The "s" key does no longer work
for me as announced, what shall I do".
Besides: Wasn't someone working on a new GUI/menu system? Wouldn't it be a
good idea to couple implementations of modified keys to that of the new GUI?
Otherwise, I could imagine some better bindings and think it's a good idea
to make a general revision of the historically developed bindings (the
proposed change of x/X included). Given the new keys are readily accessible
in keyboard.xml, I could try to catch up with a new cheat sheen then as soon
as possible.
Regards, Michael
--
Michael Basler, Jena, Germany
[EMAIL PROTECTED]
http://www.geocities.com/pmb.geo/
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
