mouse wheel: where to set scrolling speed?

[star-buck]

mouse scrolling in most plasma areas with side scrollbar is too slow default in kde 5.19 manjaro.
Where to set/speed up the pixels or steps per scrollwheel tick like it was possible?

[star-buck]

any gtk app like e.g. firefox also has much faster default scrolling, so currently it is severely inconstent...

[Pointedstick]

On Wayland, you can set the scroll speed in the mouse KCM from Plasma 5.19 onwards; see https://bugs.kde.org/show_bug.cgi?id=403842.

Apparently it wasn't possible to easily do on X11. The Enioka contractors worked on this and might know more.

[star-buck]

It was possible and working fine for me all the time before.

…

On Jul 24, 2020 15:49, "Nate Graham" ***@***.***> wrote: On Wayland, you can set the scroll speed in the mouse KCM from Plasma 5.19 onwards; see https://bugs.kde.org/show_bug.cgi?id=403842. Apparently it wasn't possible to easily do on X11. The Enioka contractors worked on this and might know more. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#237 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGNDBS3LWA6KMYNYAF322DR5GGPFANCNFSM4PGC3WEA> .

[Pointedstick]

When using the older evdev driver, yes. And as far as I can see, it still works on X11. However when using the newer Libinput driver, libinput itself does not actually support this feature natively, so it has to be done at a higher level. On Wayland, we can do it in KWin, which is what we've done. On X11, it would have to be implemented in xf86-input-libinput. There is in fact an open patch to do this: https://gitlab.freedesktop.org/xorg/driver/xf86-input-libinput/-/merge_requests/12

The maintainer would need to accept that patch though.

[davidedmundson]

I think Starbuck is referring to the Qt specific WheelScrollLines config value?
That is currently surfaced only in the ev backend despite being agnostic to the backend

[star-buck]

Thanks for the nice explanation!

…

On Jul 27, 2020 17:48, "Nate Graham" ***@***.***> wrote: When using the older evdev driver, yes. And as far as I can see, it still works on X11. However when using the newer Libinput driver, libinput itself does not actually support this feature natively, so it has to be done at a higher level. On Wayland, we can do it in KWin, which is what we've done. On X11, it would have to be implemented in xf86-input-libinput. There is in fact an open patch to do this: https://gitlab.freedesktop. org/xorg/driver/xf86-input-libinput/-/merge_requests/12 The maintainer would need to accept that patch though. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#237 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGNDBTQS2G4DU4WY5WLQKTR5WOUXANCNFSM4PGC3WEA> .

[star-buck]

eV backend?

…

On Jul 27, 2020 17:50, "davidedmundson" ***@***.***> wrote: I think Starbuck is referring to the Qt specific WheelScrollLines config value? That is currently surfaced only in the eV backend for some reason despite being agnostic to the backend — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#237 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGNDBQM2HEMCA4EIYTZBNDR5WO5XANCNFSM4PGC3WEA> .

[Pointedstick]

That is currently surfaced only in the [evdev] backend despite being agnostic to the backend

Ah, that would indeed be a real bug. Of course it would only affect Qt apps so we would probably get complaints that it didn't work for Firefox, Chromium, GTK apps, etc. Unless there's an equivalent setting we can have it also set for them.

Thanks for the nice explanation!

You're welcome!