Fusion
Fusion copied to clipboard
dphfox
Hysteresis modelling
Currently, systems built with Fusion do not generally depend on the previous state of the system, outside of animation primitives such as tweens and springs. While this is generally the best place to start when it comes to modelling most systems, some systems depend on historical states to determine their current state. This is a property formally known as hysteresis: https://en.wikipedia.org/wiki/Hysteresis
It might be worth stepping back and considering how exactly to best model systems with hysteresis. Right now, we depend on the user simply saving their own state, but common implementations of this often goes against the idea of having all state on the reactive graph and might have implications down the line when it comes to implementing features like stateful reloads or history reconstruction. If a good-enough general model for hysteresis can be found that can more elegantly model the kinds of hysteresis most often found in UI (for example, the aforementioned animation primitives, in addition to user-defined hysteresis) then we might be able to save ourselves a fair amount of work down the line when it comes to accommodating for these more stateful systems.
