-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow "acceleration" option for scrolling #13
Comments
ah. sorry for the late answer. got lost in some place without electricity nor phone data 😅️ anyways, i need to explore more the macOS APIs but as far as my investigation goes there doesn't seem to be any (nice/easy?) ways to handle that. i'm planning to add another mode, without holding keys (see #6). probably by the time i'll have gathered more info and will have a better idea of what's possible and what's not. thanks for taking the time to raise the idea. |
FWIW, acceleration would probably solve the same use case as my FR #17 (which is, basically, wanting to scroll quickly through a page to find something I noticed but lost place of) |
acceleration is another beast. not even sure it's possible without dealing with super low level shits. |
To enable smoother scrolling, I think it would be beneficial to have an acceleration parameter in the settings. This would essentially enable scrolling to start slow and ramp up to full speed when using
j
ork
. Not only does having a small amount of acceleration feel more natural, it also enables smaller scroll motions when tapping j or k quickly as the application doesn't immediately jump to a full-speed scroll.This should definitely be an optional parameter, as I know many people dislike scroll acceleration, but it could help Scrolla feel a bit less "abrupt" when trying to scroll smaller motions.
Edit: I would suggest this should be a numeric parameter in ms. Essentially: "Acceleration Time: 0ms" would be the current behavior. Anything >0ms would be the time it takes to accelerate from motionless to full-speed.
The text was updated successfully, but these errors were encountered: