Option to disable kinetic scrolling

[DataBeaver]

I have a mouse with a freely rotating wheel for quick scrolling. When looking through a long history I like to set the wheel spinning and then instantly stop when I see the thing I want. However Mirage's kinetic scrolling can easily scroll several screenfuls past the point where I wanted to stop. It's possible to effect an instant stop by pressing a mouse button, but this is an extra action I have to perform with my fingers compared to every other program. Given that the freely rotating wheel already does the inertia part on the physical device, I think a setting to disable kinetic scrolling would be appropriate. Maybe even make it the default when using a mouse, because users of traditional clicky wheels probably don't expect it either.

[vSLG]

@DataBeaver, how does #43 affect your scrolling despite the "trackpad" name?

[DataBeaver]

It does prevent the issue of scrolling past where I wanted to stop, but it also seems to be ignoring some wheel events when turning the wheel very fast.

[DataBeaver]

Actually, wheel events being ignored is probably not because of this. It happens without the modifications too. And there seems to be some kind of threshold for the event rate above which the scrolling suddenly speeds up significantly.

Setting the flickDeceleration property in HListView to a large value solves the stopping issue in what I feel is a more elegant way. Values in the range of 10000-20000 seem good, but obviously it can't just be statically set to something that large or it will make scrolling very annoying for touch users.

[vSLG]

@DataBeaver, it may not be ignoring your events. Wheel events that happen faster than refresh rate, are summed up. So it's not ignoring, but summing up scroll events. Flickable component (which ListView and GridView inherits from) has a property maximumFlickVelocity. I suggest you trying to change its value to 10000 instead of 4000. It is defined here. Also keep your flickDeceleration higher.

I have thought about increasing maximumFlickVelocity when the option useTrackpadFix is enabled. On my trackpad, I can barely feel a speed limit.

[DataBeaver]

maximumFlickVelocity doesn't seem to affect it. The feeling of wheel events being eaten happens at low speeds. If I'm at the bottom of the timeline and quickly turn the mouse wheel upwards, it will then take only two slow clicks of the wheel to get back to the bottom. If I do the same thing in a web browser, it will take 6-8 clicks.

It might not be explicitly ignoring wheel events, but if each event just resets the flick speeds instead of directly moving the scroll position, the effect is much the same. When multiple events occur in quick succession, the previous flick has not had time to complete and the total distance scrolled will be less than if those events came at a slower pace.

[vSLG]

@DataBeaver, I made some changes to improve scrolling precision on trackpads. How is it behaving on your device? In here, I can make very small amount of scroll and scroll at lightning speed and stop immediately.

[DataBeaver]

With the latest changes it works more like a traditional, non-touch application. Which is what I want when using it with a traditional, non-touch mouse.

[mirukana]

The PR has now been merged.

[toger5]

without the kinetic scrolling the speed is just much to low. how can i change that value (the max kinetec speed property has no effect)

[mirukana]

Added a nonKineticScrollingSpeed setting in 7587e55, you can set for example 2.0 to scroll twice as fast.

[toger5]

I installed the toolchain and compiled the dev branch to test 7587e55. Ther is an error when running. I will try in the upcoming days. Or open an issues if that error stays

[toger5]

Okay that was totally my fault.
i didnt install the requirements.txt with the dev branch but with master. looked through your latest commits and found that you added plyer.
now it works!