For the moment the default publisher just uses the the
/systems/electrical/[volts|amps], but aircraft with better
electrical simulations can define their own publisher to
pass in correct data as required.
The G1000 highlights the active NAV and COM radios in cyan.
In the NAV case, this is the radio being used by the CDI.
In the COM case, this is the COM radio selected on the audio panel.
Previously it was difficult to create custom EIS as paths
needed to be defined in multiple places.
This change creates a hash of id and paths to make this easier
in the future.
Previously the GenericFuelPublisher would barf if tank contents
weren't defined properly with numbers.
Also the XML and .ac files were inconsistent in their use of PANDown
vs PanDown.
Both spotted by Mark JOSEPH (ePilot). Now fixed.
- 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
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.
/instrumentation/FG1000/adc-update-frequency can optionally
be set to control the update frequency of the main ADC information.
Set to "0" to update every frame.
Periodically (default every 5 s), publish all properties
being tracked by the TriggeredPropertyPublisher.
This ensures that clients created after the TriggeredPropertyPublisher
will receive values for properties that change rarely (e.g. NAV/COM)
- Add fgcommands FG1000HardKeyPushed, FG1000SoftKeyPushed, to
simplify bindings from model XML. See FG1000/Nasal/commands.nas
- Use Device ID to ensure commands affect only the device to which
they belong. Navigation data, FMS, EIS and ADC information is shared
across all devices.
ConfigStore for storing and retrieving config settings (needs XML import/export)
Header display with 4 different header fields (all configurable)
Publisher for ADC and FMS.
