Hi,
just dumping two very similar issues here that might be worth to fix together ("stable selection"):
When selecting a text with the mouse and scrolling down while the mouse is still pressed, releasing the mouse button should not cause the scroll view to jump back to the beginning of the selection. When selecting a text with the keyboard (e.g., shift + arrow down) and scrolling down, pressing shift + arrow down again should not cause the scroll view to jump back to the beginning of the selection.
Hm ... the relevant senders are TextMorphForEditView>>#mouseUp: and TextMorphForEditView>>#keyStroke: ... PluggableTextMorph>>#scrollSelectionIntoView: always scrolls both ends of the selection into view ... Ideally, the editor could indicate which ends of the selection should be scrolled into view ... similar to #userHasEdited?
Best, Christoph
--- Sent from Squeak Inbox Talk
On 2021-05-28T12:54:07-05:00, christoph.thiede@student.hpi.uni-potsdam.de wrote:
Hi Marcel,
sorry, somehow I must have lost track of this discussion. :-)
What's exactly the benefit of putting this extra effort into the implementation? Under which circumstances is that extra scrolling a distraction? What do you want to do after "select all"? For all that we know, it might be accidental in other systems. :-)
I use this quite often in non-Squeak systems to copy/backup a text somewhere else but I want to keep reading it from the latest position. If the scrollbar jumps to another position in this case, I need to scroll back to the original position. This can, especially in longer texts, be a very tedious task ... Just stumbled again upon this.
Another argument might be that neither jumping to the beginning nor jumping to the end of the text makes ultimate sense to me.
Yet, I do like "visual stability" for such interactions. Maybe we can find a better "rule" to achieve that. Or maybe we can establish a paramter to "selectFrom:to:". There is already "invisible selection". Maybe we can add "stableSelection"? Or something like that.
As mentioned earlier, I am very open to alternative implementations. :-) I'm not very deep in the editor's implementation, would you maybe like to propose a concrete pattern?
Best, Christoph
Carpe Squeak!
Sent from: http://forum.world.st/Squeak-Dev-f45488.html