2,561
edits
Recommended Property Tree Enhancements: Difference between revisions
Recommended Property Tree Enhancements (view source)
Revision as of 18:54, 28 September 2008
, 28 September 2008→No concept of (exclusive) property ownership
| Line 18: | Line 18: | ||
So that, one change (write access) to such a property may result in multiple subsequent write accesses '''to the same property''' by its registered listeners. | So that, one change (write access) to such a property may result in multiple subsequent write accesses '''to the same property''' by its registered listeners. | ||
This is problematic in that property tree state may be mutated and invalidated by its own registered listeners. And for the majority of FlightGear components relying on tied property listeners, this would indeed result in undefined behavior and can be considered troublesome, because conceptually components such as an FDM engine will normally require exclusive write access to certain output properties. | This is problematic in that property tree state may be mutated and invalidated by its own registered listeners [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg02423.html]. And for the majority of FlightGear components relying on tied property listeners, this would indeed result in undefined behavior and can be considered troublesome, because conceptually components such as an FDM engine will normally require exclusive write access to certain output properties. | ||
=== Differentiating between "active" and "passive" listeners === | === Differentiating between "active" and "passive" listeners === | ||