- make t/T action press and hold, with some acceleration factor and
clamping to a maximum rate. (Avoids confusing latching-mode of
previous system(
- show the local time of day while adjusting.
Values are based on some experimentation, feedback welcome on the
mailing list.
This is temporary (hopefully!), to allow experimentation with different UX options in the near future. Right now it basically does nothing. As part of this, factor mouse-mode cycling into a separate command, and add some feedback. Feedback mechanism needs work, currently abusing the copilot facility.
Removing the currently unused keybindings for [Shift]I used
for cycling of HUD types. Also remove this from the help
dialog.
May be re-added for the next release, but currently there is
no HUD-type cycling implemented.
make options
--wind=nnn@mm
--visibility
--visibility-miles
--ceiling
--turbulence
work again. These options now write properties in the
/environment/config/presets
branch. The values will be applied in the property-rules
in FGDATA/Environment/interpolator.xml
Corresponds to commit e86cecf4704a4bdcf43114245d8ac94adb1f1eef
in fg/next
At the moment this dialog simply misleadingly states that we are not
tuned to any ATC service regardless of the radio settings, so better
to disable it for the release.
split AI carrier options to its own menu
moved "advanced" menu items to Debug
removed several redundant items
rationalised the placement of some items
started adding keyboard shortcuts
TODO: reinstate AI Scenario menu item (position to be conmfirmed)
get feedback
add more : keyboard shortcuts
Note that this key does sometimes fail to work. This is caused by the
way our keyboard works ATM. On an (US)English keyboard : and ; are on
the same key. If you do Press-Shift >> Press-: >> Release-Shift -> Release-:
then not the ':' is released, but the ';'. The ':' remains registered as
pressed, so the next press fails. Another press restores the function.
We fixed this for the letter keys, as it is safe to assume that 'a' and
'A' are on the same key. Unfortunately, we can't make such assumptions
for non-letter keys. We should really track the HW-key numbers, not
the symbols printed on them!
dialog when one actually wanted to switch virtual desktops. There's no need
for a keyaboard shortcut, as the dialog is available from the menu and not
needed that often.
1) The chat menu will now select the runway closest to the aircraft
when the aircraft is on the ground, or very low (< 100ft). This
handles the case where the user has selected a runway explicitly,
e.g. 01R for KSFO take-offs for noise abatement. My thanks for
AnMaster for pointing this out on IRC. Note that above 100 ft, the
wind-appropriate runway will still be used.
2) Change to keyboard description for the - key, as pointed out by
Melchior.
- rename prop-key-handler.nas to prop_key_handler.nas (the hyphens were
intentional, exactly to *make* using it as namespace less inviting,
but times change ...)
- add property browser binding to the '/'-key for when the property key handler
is turned off (/sim/input/property-key-handler=0). If it's on, use /: or
/<property>: to open the browser.
- run keyboard event listener only when property key handler is active
I hope that the '/' key can keep this binding even after a keyboard review.
The '/' is just the most natural key for dealing with properties, and it's
far less prominent on non-US-keyboards (e.g. Shift-7 on German keyboards),
so it's not really very well suited for important aircraft functions, anyway.
But I don't insist. :-)
