Worth mentioning Flickable's mouse wheel support is also pretty poor. If you move the wheel too quickly the Flickable may ignore the movement completely. If you move the wheel slowly that can make the scrolling go much faster.
Mouse wheels are relevant because it's the same code path as touchpad scrolling. High precision touchpad scrolling just emits smaller fractional values (float/QReal) of what would be a mouse wheel increment. And it works great everywhere except for Qt Flickable, which Unity8 uses a lot. :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1605513 Title: Touchpad scrolling in Flickables is disproportionately faster than mouse wheel scrolling Status in Canonical System Image: Confirmed Status in qtdeclarative-opensource-src package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Invalid Bug description: Touchpad scrolling in dash and system settings is disproportionately faster than mouse wheel scrolling I can only say this with confidence today because I implemented accurate smooth scrolling in Xmir yesterday, so I know how it should behave. It's possible QtMir is overreacting to the large number of events that touchpads generate compared to a mouse wheel, without taking into account the scroll magnitude of each one is smaller. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1605513/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
