Version: (using KDE KDE 3.5.8) Installed from: SuSE RPMs It would be great (*) to being able to configure MMB press as start of scrolling and release as the end (or hold as scroll state). This way user could run Konqueror for example, hold MMB and move slightly mouse up/down/right/left and scroll the content in that direction. The more she/he moves the mouse the faster is scrolling (times configurable acceleration factor). (*) but not only great because great: a) less key pressing, only one instead of two (when using mouse wheel) b) just one key press instead of constant scrolling c) it would be a relief for people with RSI
Btw. it could be named drag&scroll (tm) :-)
I extend this wish even further. MMB could be a modifier to scroll, but some key could be too, for example alt. So now, user could: * press alt and just move mouse to get scroll * press MMB and move mouse to get scroll * press alt and use arrow keys to get scroll * press MMB and use arrow keys to get scroll (this one is not likely, but it is a possibility of course) MMB and alt are just examples here. ADMIN NOTE: could someone please add phrase "scroll wheel substitution" to the summary. Duplicate detection will be easier.
KHTML actually implements this, albeit a bit differently. Unfortunately, the configuration option for enabling it is hidden quite hidden as well: After disabling "Middle click opens URL in selection" (Settings -> Web Browsing -> Mouse Behavior), you can scroll using the MMB. The way it's implemented here, scrolling doesn't start/stop on mouse press/release, but is started on MMB click and stopped on the next MMB click. Personally, I would prefer the reporter's suggestion (scrolling on MMB hold), because - we wouldn't have to sacrifice the ability to act on MMB click (paste clipboard), so it could be enabled by default. - this is the way it's done in other applications (Firefox/MS Office on Windows) Of course, I would love to see MMB scrolling in other applications / KParts as well (webkit part and okular are obvious candidates IMHO).
This is heavily related to bug 83481 and therefor marked as duplicate. *** This bug has been marked as a duplicate of bug 83481 ***