https://bugs.kde.org/show_bug.cgi?id=495617
--- Comment #11 from cwo <[email protected]> --- (In reply to Daniel (NIICKTCHUNS) from comment #10) > Just a question, does this work EVERYWHERE or it only works on scrollable > surfaces? Some games and programs use the scrollwheel/scroll click to do > some actions, like Blender, Minecraft and etc. On Windows this only works on > scrollable pages, tho it seems to be more related to the program rather than > the system ability to do this type of scrolls. Everywhere. It's an upstream libinput feature, and its main function is scroll wheel emulation for pointer device categories that typically do not have any (such as trackpoints/pointing sticks). As such it pretty much has to work in all the places where a scroll wheel could potentially do something, which is everywhere. With the pre-exising non-locking version, regular middle click works as normal, but you can't middle-click drag at all. With the new locking version, middle-click will always enter this mode (but you can do a regular middle-click by pressing the button twice, and this does allow you to middle-click drag this way). It's superficially similar, but quite distinct from Windows auto-scroll. You are right that to implement that kind of behavior, it's likely much easier on the application side (which knows whether the click is in a scrollable view and whether it's over anther thing that should receive middle clicks instead of entering this mode). Some applications, such as browsers, already implement this as an option. (And enabling this lock feature would interfere with that). -- You are receiving this mail because: You are watching all bug changes.
