On 06.10.2011 12:43, Vivian Meazza wrote: >> > Maybe because some properties are directly tied to C++ variables and >> > can't have a listener. >> > > That is a reasonable theory, and one which we have tried to test - but some > tied variables seem to work while others don't: is this consistent with your > analysis?
When a property is tied to a C++ variable and the C++ variable is changed directly (only possible in the C++ code), then the property's listeners won't fire. The property has no way of knowing about the change. However, when someone writes to the tied property using the "normal" property interface (setprop in Nasal or via the C++ SGProperty::setValue methods), then property's change listeners should fire normally. So, it depends on how a value is changed. But generally listeners aren't guaranteed to work with tied properties... cheers, Thorsten ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
