The "cycle view" key settings aren't needed any more, because we
do now cycle via Nasal's stepView(), and this does already take
different numbers of views into account.
Of course, this makes changes to map.{tex,pdf} necessary.
One thing I maybe should add to the doc is that the order of operation is
always:
1. scale (multiplication)
2. offset (addition)
3. truncate (truncation)
This will matter when, for instance, converting from Fahrenheit to Celsius.
The normal formula is C = (F - 32) * 0.55555556. The operator precedence
above requires a new formula, C = (F * 0.555555556) - 17.777777777.
controls in the cockpit vs. which wheels they apply to. FlightGear now
sets /controls/gear/brake-left, /controls/gear/brake-right, and
/controls/gear/brake-parking. It should be up to the FDM to sort out
which wheels under which circumstances are affected by these controls
and ultimately what happens to the physical motion of the aircraft.
First, I've attached a copy of the Logitech WingMan Force 3D XML
file "wingman-force-3d.xml" I put together after getting one of
these for Christmas. (It would be nice if the force feedback worked,
but I haven't had time to play with it that much. Come to think about
it I'm not even sure forece feedback works under Linux in general.)
Besides providing the new file I also edited the higher-level
/FlightGear/joysticks.xml file to add the description for this joystick
as follows:
diff -n joysticks.xml_orig joysticks.xml
a22 1
<js-named include="Input/Joysticks/Logitech/wingman-force-3d.xml"/>
/sim/input/selected/engine[n] properties. Also, new properties get
empty string values (which are boolean true in Nasal, maybe that
should be changed?), so test for numeric truth.
Move the "tip popup" code from view.nas to a new gui.nas module, and
make it generically useful.
Wire up flap steppings for the 747 as an example of per-aircraft
flaps.
Realtime-based property slewing, to eliminate dependence of trim and
view direction rates on frame rate.
