|
From: James T. <ja...@fl...> - 2023-06-08 09:24:37
|
> On 7 Jun 2023, at 13:31, Benedikt Hallinger <be...@ha...> wrote: > > Hm, and what is your advice for me in this instance then? I would ‘recommend' you listen(er) to the original properties if possible (as opposed to the aliases); to me that is a less ugly hack than the 10Hz timer approach. Of course this is ‘less bad of two options’ choice. I was/am hoping some other core devs will comment & remind me on the discussion around firing value-change on aliases, since we have talked about it before. The code change is quite easy, it’s the unforeseen consequences I worry about. I wonder if we could make it opt-in, i.e alias alias-with-listeners .. via an option flag to the alias() call. The change is basically to make alias() also add a proxy listener to its target. Kind regards, James |