Hi,
I have just commited some changes to the xml autopilot. Along with a tiny
bugfix comes a new feature which now allows more than one <autopilot>
definition in the aircraft's -set.xml.
You may now do something like this:
<sim>
<systems>
<autopilot>
<path>Aircraft/Hansajet/Systems/Hansajet-flightdirector.xml</path>
</autopilot>
<autopilot>
<path>Aircraft/Hansajet/Systems/Hansajet-autopilot.xml</path>
</autopilot>
<autopilot>
<path>Aircraft/Hansajet/Systems/Hansajet-digitalfilters.xml</path>
</autopilot>
</systems>
</sim>
Each <autopilot> element creates a new instance of the well known
FGXMLAutopilot class which is added to a newly created SGSubsystemGroup. This
subsystem group is added to the subsytem manager instead of the previous
single instance of the autopilot.
The idea behind this change is to be able to keep sophisticated autopilot
configurations maintainable.
No functional changes should happen to existing autopilots.
Torsten
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
