Bug 247313

Summary:	scroll based on speed of mouse wheel movement
Product:	[Unmaintained] kdelibs	Reporter:	KDE Brainstorm Submissions <brainstorm>
Component:	general	Assignee:	kdelibs bugs <kdelibs-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	wishlist	CC:	alvaro.mtr
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Unspecified
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description KDE Brainstorm Submissions 2010-08-11 01:29:25 UTC

Version:           unspecified (using Devel) 
OS:                unspecified

Similar to some UIs like Apple's iPod Touch where if you move your finger (or say mouse scroll wheel) slowly then the page scrolls smoothly and slowly.

But if you quickly flick your finger up or down (or quickly scroll the mouse wheel) then the window/page should smoothly accelerate/decelerate (use motion dynamics) so that you can scroll large/long pages/windows faster.

Right now I have to keep **** the mouse scroll wheel many many times to scroll from the top to bottom of a webpage and a "workaround" is to click and drag the scrollbar but that defeats the utility of the scroll wheel.

This could be either implemented in a generic KDE widget so that it works for multiple apps like Dolphin, Kate, Konquerer etc? Or perhaps use the new QT animation framework somehow? If performance/flicker is a problem then this can be a KWin effect to enable only when desktop effects can be supported/enabled in the hardware...


This feature request was originally submitted through KDE Brainstorm, and has been submitted to Bugzilla due to popular demand. Original idea: http://forum.kde.org/brainstorm.php?mode=idea&i=61210

Reproducible: Didn't try

Comment 1 alvaro 2013-01-24 17:14:49 UTC

it would be great also if there was an option for smoth scrolling

Comment 2 Christoph Cullmann 2024-09-14 16:17:47 UTC

Hi,

kdelibs (version 4 and earlier) is no longer maintained since a few years.

KDE Frameworks 5 or 6 might already have implemented this wish.

If not, please re-open against the matching framework if feasible or against the application that shows the issue.

We then can still dispatch it to the right Bugzilla product or component.

Greetings
Christoph Cullmann