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.
* this was previously included in many glider aircraft in FGAddon, thus now saving space and maintenance work
* it also adds the noshadow animation to make the woolthread compatible with Compositor
* Please note: I was not able to figure out the original author (not me) of the model, texture and xml, but as far as I can see, it should be fine license-wise, since it was included in GPL FGAddon aircraft for ages
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.
Previously select XPDR->CODE->7 and then another number caused very odd
transponder codes. Turns out this was due to extra whitespace in the
label causing various string concatenations and evaluations to fail.
Previously a completely new PFD or MFD was created when the Debug
menu items were used. This cause significant slowdown if used
multiple times. Now we just create one instance of each and re-use it.
Also clean up redundant code in the GUI.
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)
