Bug 254709 - In "System Settings > Input Devices > Mouse > Advanced > Mouse Wheel Scrolls By," add page up/page down option
Summary: In "System Settings > Input Devices > Mouse > Advanced > Mouse Wheel Scrolls...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_mouse (show other bugs)
Version: 1.0
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: Marie Loise Nolden
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-20 01:09 UTC by W5WMW
Modified: 2024-03-25 01:49 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description W5WMW 2010-10-20 01:09:19 UTC 
Version:           1.0 (using KDE 4.5.1) 
OS:                Linux

The current options for KDE 4.5.1 "System Settings > Input Devices > Mouse > Advanced > Mouse Wheel Scrolls By" allow for one to twelve lines per mouse wheel scroll notch.  Please consider adding another option—allow us to set the mouse control to where each scroll wheel notch scrolls by page—basically giving the mouse wheel the option of acting exactly like the Page_Up and Page_Down buttons on the keyboard (settable as normal or reverse in direction, of course).

Not too hard, right?  Thank you very much.

Reproducible: Didn't try




OS: Linux (i686) release 2.6.35-22-generic
Compiler: cc
Kubuntu 10.10 (Maverick Meercat) desktop i386 and amd64
ZaReason Teo Laptop Computer
Comment 1 W5WMW 2010-10-20 01:25:30 UTC 
Note:  Other operating systems or the proprietary MS-Windows drivers of many mice already support this option that I (and I'm sure others) wish.
Comment 2 Rob Kam 2021-07-20 14:47:14 UTC 
*** This bug has been confirmed by popular vote. ***
Comment 3 Nate Graham 2024-03-25 01:49:02 UTC 
Hello! This Bugzilla ticket concerns support for the non-Libinput version of the Mouse page, which is no longer supported in Plasma 6. The scroll setting in the Libinput page is abstracted rather than promising specific amounts of scrolling (which is impossible; it would be a broken promise), and as such, implementing what's requested here is now out of scope.

Thanks for your understanding!