While IMO usability is still horrible I'm not sure what to do about it. Its possible that the scrolling doesn't work for me very well for hardware reasons, or that the current implementation just doesn't work very well for desktop systems (could even be resolution dependent). I think we'll leave it just as it is for the time being, because otherwise we'd likely have to do something more or less from scratch.
The symptoms I see are:
- minor touches on the touchpad result in the view dashing off in one direction, it's very hard to just scroll a little.
- scrolling full speed looks ok, but stopping where I want is again pretty hard
What I want:
- what my browser does
The browser scrolling seems much more direct and much better suited for interaction with the mouse.
Scrolling continues to suck with qt 5.9. The QQC2 ScrollView does nothing useful to change that.
I found a way to address the issue, however we'll have to figure out parameters that work with a variety of hardware. The current solution works for me, but probably not everyone.
Also, the same fix is in principle required everywhere where a flickable is involved. That includes at the very least the composer editor as soon as we switch to qqc2 there (because the old scrollview essentially implemented a similar fix to what we have in Kube.ListView now).
Scrolling with a proper mouse-wheel is apparently still too slow, but in general the issue is addressed.