Johan G wrote in Sat Jul 19, 2014 9:20 pm:Philosopher wrote in Mon Jul 14, 2014 7:01 pm:You can add a flag to setlistener to have it run
only when the value has changed, so that's not an issue. (It just isn't enabled by default – aka activate each write is the default behavior.)
To a layman that is rather counterintuitive. I would for sure a listener to only react on changes.
Actually, it isn't: a listener responds to updates - it can only tell if there's been a change if it processes all updates. So it kinda makes sense once you think about it.
Imagine a real life analogy: a listener processing news announcements, it can only tell if there's new information announced if it's processing ALL announcements/news.
We have a number of way to trigger listeners by simply updating it with the same value.
And no, it's not a safeguard - "tied properties" were a performance hack over a decade ago, and even its creators called it a "brain fart" back then, tied properties are causing a lot of challenges in FG unfortunately. These days, people should normally be using propertyObject<> instead.