While messing around with an aeromatic generated Lancaster model I
discovered that there are a few inconsistencies in keyboard.xml. It allows
you to reduce the magneto setting on 4 engines, but will only increase it
on 2, which tends to result in a somewhat circular path from the end of
the runway
Oops didn't even notice that when looking the other day. This has been added
to the CVS now.
Best,
Jim
Jon Stockill [EMAIL PROTECTED] said:
While messing around with an aeromatic generated Lancaster model I
discovered that there are a few inconsistencies in keyboard.xml. It allows
you to
I'd like to propose some changes to keyboard.xml:
1. There's no key for the wing leveler. Ctrl-w is still free and consistent
with the other autopilot settings.
2. I have never understood why the gear is a property-toggle. It is quite
common to land with gear down, but it's hard to tell
Melchior FRANZ [EMAIL PROTECTED] said:
I'd like to propose some changes to keyboard.xml:
1. There's no key for the wing leveler. Ctrl-w is still free and consistent
with the other autopilot settings.
When I redo the autopilot code (might start next week) it might be appropriate
to
I was having a fiddle with keyboard.xml to support a UK keyboard, and
discovered that the characters £ and ¬ (which are shift-3 and shift-key
to left of 1) break the XML parser. Is this intentional?
Also, in the grand re-organisation of the XML files that appears to be
planned, do we need to
Richard Bytheway writes:
I was having a fiddle with keyboard.xml to support a UK keyboard, and
discovered that the characters £ and ¬ (which are shift-3 and shift-key
to left of 1) break the XML parser. Is this intentional?
By default 8-bit XML files use Unicode UTF-8 encoding. That's
Richard Bytheway wrote:
I was having a fiddle with keyboard.xml to support a UK keyboard,
and discovered that the characters £ and ¬ (which are shift-3 and
shift-key to left of 1) break the XML parser. Is this intentional?
Also, in the grand re-organisation of the XML files that appears
