With autopause active, selecting text pauses scrollback (this is good) but then unselecting doesn't unpause (I think this is bad) even though scroll is at the bottom and nothing is selected.
select pauses, but unselect doesn't unpause
Posted by Fiendish on Sun 12 May 2019 09:44 PM — 3 posts, 11,359 views.
Strictly speaking, clicking with the mouse outside a selection, when a selection is active doesn't really unselect, it starts a new selection.
So yes, it unselects the old selection, but the a one has been started.
So, for example, you have scrolled back and selected the text:
But you meant to select "Cheery" as well. So you click in front of "Cheery" and then shift-click after "heard" giving:
It would be very annoying if the paragraph you were looking at suddenly vanished just because you are tweaking your selection.
Yes, well that wouldn't be as bad I suppose. Although how often does that happen on an active MUD?
There seems to be a bug in the code. If you press the "pause" button (the one with paws as an icon) the status line immediately reads MORE when it should read FREEZE. That suggests to me that the "at end of buffer" test is wrong.
I'm a little reluctant to fiddle because changing something like that can introduce other bugs, but if you can spot the issue by all means let me know.
So yes, it unselects the old selection, but the a one has been started.
So, for example, you have scrolled back and selected the text:
Cheery laughter can be heard in this section of Horizon Road.
^^^^^^^^^^^^^^^^^^^^^
(selection)
But you meant to select "Cheery" as well. So you click in front of "Cheery" and then shift-click after "heard" giving:
Cheery laughter can be heard in this section of Horizon Road.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
(selection)
It would be very annoying if the paragraph you were looking at suddenly vanished just because you are tweaking your selection.
Quote:
... even though scroll is at the bottom ...
... even though scroll is at the bottom ...
Yes, well that wouldn't be as bad I suppose. Although how often does that happen on an active MUD?
There seems to be a bug in the code. If you press the "pause" button (the one with paws as an icon) the status line immediately reads MORE when it should read FREEZE. That suggests to me that the "at end of buffer" test is wrong.
I'm a little reluctant to fiddle because changing something like that can introduce other bugs, but if you can spot the issue by all means let me know.
Arguably, what I described above could also apply if the window scroll was at the bottom. Let's say you see something interesting which you want to copy/paste, so you click to start selecting it. Then, new stuff from the MUD arrives, and you have to chase the phrase that you were about to shift-click as it sails up the screen.
So I think that you could argue that starting the selection process is justification for freezing the output scrolling.
So I think that you could argue that starting the selection process is justification for freezing the output scrolling.