Autopilot configuration reference: Difference between revisions

Jump to navigation Jump to search
m
→‎Structure Of a Configuration File: Template:Note → Template:Tip
(→‎Flip Flop: Notes about some troubles I have had)
m (→‎Structure Of a Configuration File: Template:Note → Template:Tip)
Line 38: Line 38:
</syntaxhighlight>
</syntaxhighlight>


{{note|Using aliased property names is good style and makes the configuration file more readable. For complex autopilot systems spread over multiple autopilot configuration files, the params section may be included from an external file using <tt><nowiki><params include="my-params.xml"/></nowiki></tt> to avoid duplication of code.}}
{{tip|Using aliased property names is good style and makes the configuration file more readable. For complex autopilot systems spread over multiple autopilot configuration files, the params section may be included from an external file using <tt><nowiki><params include="my-params.xml"/></nowiki></tt> to avoid duplication of code.}}


The location and the name of the configuration file is up to the developer. A descriptive name like 'autopilot.xml' might be a good choice. Most developers put these files into the Systems folder of the aircraft.
The location and the name of the configuration file is up to the developer. A descriptive name like 'autopilot.xml' might be a good choice. Most developers put these files into the Systems folder of the aircraft.

Navigation menu