20,741
edits
Property tree: Difference between revisions
Jump to navigation
Jump to search
m
→The purpose of the property tree: http://forum.flightgear.org/viewtopic.php?f=30&t=28766&p=275994#p275994
m (Johan G moved page Property Tree to Property tree over redirect: Non-camel case title) |
m (→The purpose of the property tree: http://forum.flightgear.org/viewtopic.php?f=30&t=28766&p=275994#p275994) |
||
| Line 8: | Line 8: | ||
One might think of the property system as a global, normalized communication platform, where subsystems may publish variables and access other subsystem's variables. In addition, ''callbacks'' can be registered to invoke code upon read/write access of properties, which serves as the backbone for a very simple, but powerful, ''signalling mechanism'' in FlightGear. Thus, the property system acts as a routing interface, both between different high-level FG sub-systems and the outside world. Data that is required by one FG sub-system can be exposed in the property tree, where it can then be read or modified, either by other internal FG sub-systems, or by and for external input/output. | One might think of the property system as a global, normalized communication platform, where subsystems may publish variables and access other subsystem's variables. In addition, ''callbacks'' can be registered to invoke code upon read/write access of properties, which serves as the backbone for a very simple, but powerful, ''signalling mechanism'' in FlightGear. Thus, the property system acts as a routing interface, both between different high-level FG sub-systems and the outside world. Data that is required by one FG sub-system can be exposed in the property tree, where it can then be read or modified, either by other internal FG sub-systems, or by and for external input/output. | ||
There is some basic property-debugging support to FlightGear and SimGear. In FlightGear, the --trace-read option causes all read access for a property to be traced, and the --trace-write option causes all write access for a property to be traced, both through SG_LOG messages. | |||
=== Examples of use === | === Examples of use === | ||