|
From: Benedikt H. <be...@ha...> - 2023-06-06 07:35:13
|
Hi, i stripped down the code to a basic example. and that seems to work. When i have a Prop node A, and it changes its value, do the aliased props also fire a listener? A<-alias B setlistener(B) When A changes, the new value can be read from B; but does an setlistener to B also fire when the underlaying prop A changes? Am 2023-06-03 17:07, schrieb James Turner: >> On 3 Jun 2023, at 14:39, Benedikt Hallinger <be...@ha...> >> wrote: >> >> I already tried to find out why the lister does not work. >> Maybe its how i register them. > > Right, it’s unlikely you have found a way to really break something > so fundamental: much more likely: the property is re-created (so the > listener is on the old prop) or the listener itself is removed or some > other ‘weird’ thing happens. > > Can you point me at the properties which don’t seem to work? Or even > better, provide me a free-standing .nas script I can run which adds a > non-working listener to those props? (i.e independent of the add-on / > mumble / anything else, just a minimal test case) > > Kind regards, > James > _______________________________________________ > Flightgear-devel mailing list > Fli...@li... > https://lists.sourceforge.net/lists/listinfo/flightgear-devel |