Hello @jeremyruston, great work (also with the scroll binding in general).
The example I gave above still does not work, though. After some thinking, I’m not sure that it can ever work. How would the $scrollable widget know that it needs to use a different tiddler for binding? It has no reason to check if its now argument has changed as a reaction to its content being scrolled. Interestingly, folding / unfolding also have no effect. I would have expected it to use a different bound tiddler after that.
Scrolling itself is much better, but when you’re used to modern smooth scrolling it still feels a little “viscous”. Would it be possible to wait for e.g. 100 ms after the last scroll event to write the coordinates to the tiddler, maybe as an option? I can’t see a use for writing multiple updates during a single scroll operation.
Due to the timeout when reading from the bound tiddler, even synchronous scrolling of e.g. two side-by-side rivers would not be really synchronous.
I’m sorry for this late feedback. I had the Talk topic open in a browser tab for weeks and weeks, but never got around to test it until it popped up again in the release notes.
Yaisog