↑ look at project
1.1 Added support for Updaterate
updaterate on the config object to set it up.
If you use the new
updaterate feature to limit the amount of triggers on your mutation code, the extension also takes care to apply the first inital update and the last update. If you don’t want that you can disable them using the config keys
Visual explanation of
PS: As seen on the right hand side of the visualization, the check against the
updaterate is not always on the heartbeat of the interval. That is rather what Hype AnimationFrame is for. So if a mutation event falls inbetween to heartbeats (interval) and more time has passed then an interval, it gets fired. That also always sets up a delayed timeout callback to fire any cached mutations in the next interval as a final update.