20,741
edits
Property tree: Difference between revisions
Jump to navigation
Jump to search
→Introduction: http://flightgear.org/forums/viewtopic.php?f=18&t=19503#p179984
(→Introduction: http://flightgear.org/forums/viewtopic.php?f=18&t=19503#p179984) |
|||
| Line 70: | Line 70: | ||
This is why the property tree is not consistent with fixed variables, they are created dynamically, to represent a propeller plane vs Jumbo or even a "Caspian Sea Monster". | This is why the property tree is not consistent with fixed variables, they are created dynamically, to represent a propeller plane vs Jumbo or even a "Caspian Sea Monster". | ||
Many properties will be aircraft-specific, and availability may even depend on the startup/runtime settings you are using. There are a bunch of "common" properties - especially among similar FDMs and aircraft. Obviously, different FDMs/aircraft will use different properties (single piston, helicopter, jet, twin turbine helicopter etc). You may want to have a look at $FG_ROOT/Docs/README.properties. | |||
There are a couple ways that they are set, but a fair amount of them just "appear" without being documented anywhere. There are several places to look for properties; one is in the aircraft files, another is all Nasal files, and the last place (and often most useful!) is grepping (searching) through the C++ code. To determine how a property works and what it does often requires looking through any code that uses it. This is a part of FlightGear that we could certainly document better | |||
The property tree is read, written, accessed and manipulated in a variety of ways, such as | The property tree is read, written, accessed and manipulated in a variety of ways, such as | ||