From: Melchior F. <mf...@ao...> - 2007-01-21 17:23:33
|
* Martin Spott -- Sunday 21 January 2007: > Well, I didn't experience any difficulties exchanging EMails with Tat and > I'd call it a good habit to ask him before repeatingly removing a > (small) part of his aircraft configuration. Again: I did ask (see mail below). All others replied and either allowed me to change it, or changed it themselves, or announced that they'll changed it themselves with the next submission. Only Tatsuhiro didn't respond. Maybe my mail got lost or he just didn't see it. My mailbox is often filled, too, and I easily miss someone. But as it's a matter of architecture, as the aircraft was *very* new, and as the redundant code was very obviously just copied from the A6M2, with no explicit intention behind it at all, I just did what is necessary for a consistent fgfs. m. Subject: <key> def for "Propeller finer/coarser" in *-set.xml files Date: Fri, 19 Jan 2007 15:48:16 +0100 From: Melchior FRANZ <mf...@ao...> To: Stuart Buchanan <stu...@ya...>, Vivian Meazza <viv...@li...>, Detlef FABER <fa...@so...>, Tatsuhiro NISHIOKA <tat...@ni...>, Syd ADAMS <syd...@te...> Hi, I've noticed that not only old aircraft still define keys for "Propeller coarser/finer", but that aircraft are still committed with these obsolete overrides. c310 ... me :-) A6M2, A6M2b ... Syd Ki-84 ... Tatsuhiro bf109, bf109g, f4u ... Detlef c182, c182-2dpanel, c182rg ... Stuart hurricaneIIb, seafireIIIc, spitfireIIa ... Vivian Could you all please check if your aircraft *really* need this override? Note that n/N is globally defined already in $FG_ROOT/keyboard.xml. And global keys shouldn't get overridden for no good reason, let alone when the meaning remains the same anyway, or the binding is actually *worse*. (Many of the override definitions don't even use the controls wrapper!) I will fix the c310, and I've already fixed the c182 and the c182-2dpanel before I noticed that they are maintained by Stuart. (I could check these two in, too.) Please remove redundant bindings yourself, or give me permission to do it, or do it in your next update (the sooner the better). But *iff* you need to redefine global bindings while keeping the meaning, then please also use the common <desc>. Don't use "Propeller Fine" when everyone else uses "Propeller finer". These descriptions are automatically extracted and listed in $FG_ROOT/Docs/Input/keyboard/map.pdf and can't be grouped properly otherwise. (<desc> in <help> blocks are not concerned, only those in key definitions.) m. |