https://bugs.kde.org/show_bug.cgi?id=508290
--- Comment #8 from Mark <[email protected]> --- Some updates. While this definitely happened on my KDE environment (i tried it in there to be sure before i even commented), i can't reproduce that anymore. Don't know what changed besides a reboot. Changing the scroll speed in the system-settings (Mouse & Keyboard -> Mouse -> Scrolling speed) applies it just fine. No need to relog or reboot, it works in dolphin. You might want to restart dolphin though but that's about it. It's when i'm not using KDE (but am using Dolphin) that i'm facing more issues. Say in a Hyprland environment. I took a look in the code from the Mouse KCM [1] and it looks like it's using backend specific paths (x11/wayland) through kwin! Which is kind a confirmed by opening system-setting and going to the mouse settings in a desktop environment that isn't plasma, then you'll see "Querying input devices failed. Please reopen this settings module." Apparently, and this boggles my mind in disbelief, the scroll factor is a compositor or even app specific feature. Ouch! This thread [2] confirms that. There are a few different ways to go about this. 1. No config in Dolphin, you rely on compositor settings. This only works if everybody like the speed in dolphin. Hey, we're linux users with wildly diverse opinions. Are we ever gonna settle on a universal "this is an ok scroll speed" value? I don't think so. Now i've looked in hyperland, i'm using it more and more, and it does have a "scroll_factor" which defaults to 1.0. Changing that to 3.0 makes dolphin act as i want it. But everything else (chrome and other apps with scroll), men they race at the speed of light! So i think it's safe to say that a global option is not a desirable outcome. The current dolphin implementation is this option. With the caveat that you can edit dolphinrc as mentioned by Sdar. But given that this is a GUI application, it's nasty to hide it in a config variable that isn't even documented anywhere. You just happen to have to know about both KDE and Qt for this to make sense. It would be different if this were a console based app, but it's not. 2. A configurable setting in dolphin. The cleanest solution is probably to make this [3] configurable in the dolphin settings. Set a default that you like in KDE that mimics that compositor speed setting. I think this is a clean and sensible solution. It is essentially a gui way to make WheelScrollLines editable. Again, i thought this was there in the gui all along but i can't find it anywhere. [1] https://invent.kde.org/plasma/plasma-desktop/-/tree/master/kcms/mouse [2] https://discourse.gnome.org/t/add-touchpad-scroll-sensitivity-adjustment-feature/18097/36 [3] https://doc.qt.io/qt-6/qapplication.html#wheelScrollLines-prop -- You are receiving this mail because: You are watching all bug changes.
