Poor scrolling control in side panel on touchpad

tomsmekens commented 1 month ago

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

In a score, make it so that any of the dialogs in the side panel (palette, properties etc.) expands beyond the dimensions of the screen and requires scrolling to navigate.
Use a laptop touchpad to scroll up and down.
Observe the user friendliness of the scrolling.

Actual behavior: Keeping your fingers still does not stop the scrolling. It is difficult to navigate the panel because you will constantly overshoot where you actually want to be.

Expected behavior: Stopping movement with your fingers should stop the scrolling as well. That is how it usually works in programs - firefox is one example - and it's also how it works when scrolling through the score in MuseScore itself.

Supporting files, videos and screenshots

Screencast from 29-09-24 03:17:03.webm

What is the latest version of MuseScore Studio where this issue is present?

OS: Ubuntu 22.04.5 LTS, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.2-242570931, revision: github-musescore-musescore-3130f97

Regression

No.

Operating system

Ubuntu 22.04

Additional context

In the attached video, I am keeping my fingers on the touchpad the whole time. I vaguely recall that this issue cropped up starting with MuseScore 3 and has persisted all this time. I'd hoped that the new Qt would fix it, but no luck.

My model is a Dell Inc. Latitude E5470 but I've had the same issue on previous laptops from Asus.

Checklist

[X] This report follows the guidelines for reporting bugs and issues
[X] I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
[X] I have attached all requested files and information to this report
[X] I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

krasko78 commented 1 month ago

I agree. It is especially annoying for me on the palettes. Maybe we could set maximumFlickVelocity and flickDeceleration on the flickables / listviews? For me, values in the range of 800-1500 for maximumFlickVelocity and 10000-25000 for flickDeceleration seem to work best. Or those values could be dynamic, based for example on the length / height of the list / content if we don't want to lose the acceleration on long lists.

bkunda commented 1 month ago

musescore / MuseScore