2,561
edits
Recommended Property Tree Enhancements: Difference between revisions
Recommended Property Tree Enhancements (view source)
Revision as of 21:35, 21 February 2009
, 21 February 2009→No concept of (exclusive) property ownership
| Line 16: | Line 16: | ||
=== No concept of (exclusive) property ownership === | === No concept of (exclusive) property ownership === | ||
In fact, it is unfortunately even possible to easily register multiple ''writing'' property listeners for the very same property (for example, it would be possible -and has been the case in the past- that registered listeners are exercising write access to properties exclusively owned (at least conceptually) by other components, such as the FDM, whose state would then be automatically invalidated due to its registered listeners each time a property is updated). | In fact, it is unfortunately even possible to easily register multiple ''writing'' property listeners for the very same property [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg02422.html] (for example, it would be possible -and has been the case in the past- that registered listeners are exercising write access to properties exclusively owned (at least conceptually) by other components, such as the FDM, whose state would then be automatically invalidated due to its registered listeners each time a property is updated). | ||
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. | ||