Implement the Nearest Airports PFD softkey, displaying a scrollable
list of the closest 25 airports within 200nm.
Also fix a couple of minor bugs and add self-checking to the
GroupElement
Previously the FG1000 and MFD assumed that all notifications received
via Emesary had a Device_Id field. This is true for
notifications.PFDEventNotification.DefaultType but not for other
messages - e.g. those generated by the AN SPN 46 system on the
carrier.
The effect of this was that when Nimitz was loaded, the FG1000 stopped
working with various errors.
This fix checks the notification type before the Device_Id.
- Make Range knob behaviour consistent between PFD inset and MFD maps
- Add rotation animations for the HDG and CRS knobs
- Change the CRS knob behaviour:
- BARO on outer knob (consistent with FMS knob)
- CRS on inner knob
- Shift-click on inner knob to center (consistent with HDG knob)
Adds a sound frequency controller to glider-instrumentation-sdk.nas,
used for the ilec-sc7. This allows:
- Simpler <sound>.xml files to integrate the glider variometer.
- More accurate frequency scaling (frequency scales exponentially with
vertical speed, so that perceived changes in pitch are linear with
vertical speed).
- Fixes that the variometer sound would not drop at negative vertical
speeds.
- Pre-load nearest airports to remove significant freeze when the
NearestAirports page is accessed for the first time.
- Update multikey support to provide easy access to commonly used MFD
pages and access to softkeys.
Approach and GS modes - FG1000 and GFC700 can now be used for
autopilot coupled ILS or GPS approaches
Also:
- FLC mdoe now include an airspeed bug
- VDI indicator beside altitude tape now works
- Marker beacon displays O/M/I as appropriate
GFC700 now supports the Selected Altitude Capture (ALTS) and Altitude
Hold (ALT) modes.
ALTS is automatically armed in more vertical modes, and allows capture
of whatever altitude is selected.
Add Multikey support for the FG1000 (:GF and :GP) to improve useability
by allowing direct entry of strings. This is massively easier than
fiddling with the control knobs.
Also correct interface variable name "frequency" to "period", which is
more accurate.
- proper messages stack and API
- paging of scrolled-pages behind static pages works (eg RTE)
- exec API (and cancellation)
- more callbacks / overrides on actions and models
- temporary (modal) page support, eg for waypoint disambiguation
- reload command
Definitely problems in aar.nas, seaport.nas; as these were hanging off a fdm-initialized.
The others have timers that are started from a listener and as such are more suited to use maketimer rather than settimer
The modules that use the loopid technique are probably fine, but these are also more suited (and easier to understand) using a maketimer
