SUMMARY https://phabricator.kde.org/D25628 gave me this idea: Currently there are no visual controls for auto scrolling. There are just the QActions “Scroll Up/Down”, which can be added as stupid push buttons to the toolbar. I suggest to implement a QWidgetAction containing a Play/Pause button and some interactive speed control. The speed control could show something like n Pages/min or n s/Page, maybe it should be a spin box with that unit. I can’t provide a use case for automatic scrolling. But it could be nice if automatic scrolling would work with Continuous disabled or with the scrolling method described in D25628 & Bug 414688.
Automatic scrolling inherently depends on the user to fine-tune the scroll speed with their cursor positioning according to the document length, word density, and their own reading speed, right? Does it make sense for this to be a non-cursor-based action?
I am not sure what you mean. Google Chrome has autoscrolling where you middle-click on an empty area once and move the cursor to adjust the scroll speed. Okular has only the actions Shift + Arrow Key; and Shift can pause auto scrolling. So do you reference one of these?
Oh, I did not know about those Shift+up/down shortcuts! I had assumes that the only way to trigger it was using a middle-click. So yes, it does indeed seem to make sense to make this more discoverable by exposing it as an action in the UI. Not sure about putting it on the toolbar though, at least not by default. But optionally, sure.