I am using a laptop, I normally scrol with 2 fingers on the touchpad, however changing desktop with this is rather difficult because it is not very precise, and I can't do 1 scroll-click thing.
So I'd like to see a timeout of a few milliseconds that disables scrolling before activating it again, so that I could switch to a certain desktop rather than play roulette.
This is almost identical to #391551. This needs some work. It's an accessibility issue as well as an an annoyance. I often end up unintentionally scrolling desktops when I'm just trying to move the mouse cursor from the panel to a window on the desktop I just selected.
*** Bug 391551 has been marked as a duplicate of this bug. ***
I'd really appreciate some movement on this issue. It is a major source of frustration with an otherwise pretty great UI/UX.
Is it actually working at all for you? Touchpad scroll-on-the-desktop-to-switch-virtual-desktops has just been totally broken since 5.19; see Bug 419867. Or is that the issue you're experiencing?
It works for me on 5.20, what can I say…
However i'd appreciate if it did it more slowly so I didn't have to finely calibrate my fingers to trigger 1 and only 1 "scroll event"
I bet this bug has the same root cause as Bug 419867. Let me see if I can figure it out.
(In reply to Nate Graham from comment #6)
> I bet this bug has the same root cause as Bug 419867. Let me see if I can
> figure it out.
Seems like it might be related. However, I don't have any screen edge actions enabled and I don't even know how scroll wheel emulation works on a touchpad, but I certainly don't use it on purpose.
For reference, I'm on kubuntu 18.04, KDE Frameworks 5.47.0 Qt 5.9.5 (built against 5.9.5), planning to upgrade to 20.04 sometime soon.
My root issue is that I have two semi-numb fingers, so I frequently accidentally get two-fingered touchpad actions without feeling it.
I asked elsewhere about getting an optional enhancement such that touchpad scrolling would be disabled unless I was holding down a key such as Ctrl, but that didn't go anywhere. I don't want to disable it completely.
Looking into this, there is no feasible way to make just the virtual desktop switching scroll action require a bigger touchpad scroll before activating. We could make all desktop touchpad scroll actions require a bigger touchpad scroll before triggering, however.
(In reply to Nate Graham from comment #8)
> Looking into this, there is no feasible way to make just the virtual desktop
> switching scroll action require a bigger touchpad scroll before activating.
> We could make all desktop touchpad scroll actions require a bigger touchpad
> scroll before triggering, however.
That might work, but it would probably have to be user configurable because there's no way one setting will make everyone happy.
I'm starting to wonder if this is fixable.
In plasma-framework/src/scriptengines/qml/plasmoid/containmentinterface.cpp, we accumulate scroll angle deltas from QWheelEvent::angleDelta(), under the assumption that 120 is one scroll click, at which point the "I did a scroll" event fired. This works fine for mouse wheels, but for a touchpad, it results in a very small finger movement producing one scroll event. Ideally we would want for a larger finger movement to be required. A value between 240 and 360 produces a better result for my touchpad, but makes it unusably slow for mouse wheels. We need a way to distinguish between when the event comes from a mouse wheel and when it comes from a touchpad. QWheelEvent::pixelDelta() is supposedly used for this, but it always produces 0, and the Qt documentation says that it's unreliable on X11 and should not be used. :/
Not sure how to proceed.
I guess we could implement a handler for pixelDelta() and it would work for Wayland users.
If you make it user configurable, then you don't need to know mouse vs. touchpad. It could be in a config file because any particular user is probably going to adjust it once and forget it - so it doesn't have to be GUI or dynamically updated the moment it changes. (Those would be nice, but probably not worth the effort.)
Unfortunately making it user-configurable does not help; what if the user is using a laptop and has a touchpad but also has a mouse plugged in and switches between both depending on which one is closer to their hand? That's how I often work. we need the ability to distinguish between input devices programmatically, not push the burden onto the user.