13,212
edits
Autopilot configuration reference: Difference between revisions
Jump to navigation
Jump to search
m
Autopilot configuration reference (view source)
Revision as of 16:32, 30 January 2015
, 30 January 2015→Structure of a configuration file: +link: PropertyList XML files#Aliased properties
(+-Performance considerations; Documenting <params> and aliases, using README.xmlpanel as reference) |
m (→Structure of a configuration file: +link: PropertyList XML files#Aliased properties) |
||
| Line 113: | Line 113: | ||
The location and the name of the configuration file is up to the developer. A descriptive name like <code>autopilot.xml</code> might be a good choice. Most developers put these files into the <code>Systems</code> folder of the aircraft. | The location and the name of the configuration file is up to the developer. A descriptive name like <code>autopilot.xml</code> might be a good choice. Most developers put these files into the <code>Systems</code> folder of the aircraft. | ||
{{tip|Using aliased property names is good style and makes the configuration file more readable. The params section may be included from an external file to avoid duplication of code. | {{tip|Using [[PropertyList XML files#Aliased properties|aliased property names]] is good style and makes the configuration file more readable. The params section may be included from an external file to avoid duplication of code. | ||
For complex systems, spread over multiple autopilot and/or property-rule configuration files, this can greatly aid debugging and maintenance.}} | For complex systems, spread over multiple autopilot and/or property-rule configuration files, this can greatly aid debugging and maintenance.}} | ||