|
From: Benedikt H. <be...@ha...> - 2023-06-10 15:06:30
|
That proposal regarding the alias Call sounds good. > Am 07.06.2023 um 14:34 schrieb Benedikt Hallinger <be...@ha...>: > > > Hm, and what is your advice for me in this instance then? > >>> Am 06.06.2023 um 12:46 schrieb James Turner <ja...@fl...>: >>> >> >> >>>> On 6 Jun 2023, at 08:34, Benedikt Hallinger <be...@ha...> wrote: >>>> >>>> i stripped down the code to a basic example. and that seems to work. >>>> >>> >>> That is slightly what I expected, and re-assuring (waring my core-maintainer hat) >>> >>> 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? >> >> I thought this did work, but apparently it does not : aliases are bit liked tied properties in this regard. >> >> We could fix this, it would require SGPropertyNode::alias to chain to its target’s listeners. (Target nodes don’t know they are aliased, so we can’t ‘forward fire’ the aliases) >> >> I suspect people have mostly just worked around this (now I think, I have worked around it once myself) … but it breaks the useful-ness / abstraction of aliasing quite badly. >> >> Kind regards, >> James |