I’ve tried to implement synchronized scrolling. It’s an option that can be turned on in the Collection Settings. The current implementation is far from perfect, but perhaps better than nothing for some use cases…?
Interested in hearing feedback about this.
(BTW, it’s been a while, partly because the implementation turned out to be not at all straightforward, but also because I’ve been on a bit of a summer vacation for the last couple of weeks…)
Just started kicking the tires but do notice the elevator is misleading in Edit. Seems to always be at the top when returning from Display even if the end of some long text is displayed.
Not sure how I might set a location in Display to sync with Edit. Scroll position, I guess. Setting an insertion point in Edit should set the scroll position in Display to the same location. I’ll try that.
OK, I can see that now after relaunching Notenik with the option enabled in that Collection. I hadn’t before. The scroll position is roughly approximate (I can find the same text in both windows if a little higher or lower).
This may be good enough for getting from Display to Edit because Display has no insertion point. I’m not sure it’s precise enough for going from Edit’s insertion point to Display (I have to hunt around to see the effect of what I was formatting).
But I’ll keep at it to see if I can train my brain to how it works!
Elevator (draggable gray bubble showing scroll position), which goes up and comes down:
@hbowie, I saw @mrpasini’s use of elevator, and I immediately thought “Yes! That’s what it was called back in Apple’s original Human Interface Guidelines way back in the day!
I seem also to recall it being called a trolly car; perhaps that was in the Lightspeed Pascal (→ THINK Pascal) docs? I can’t find any reference to it now.
I can see how someone would come up with that, since it’s typically a long object that runs back and forth on a fixed track. (But again, a new one on me.)
