https://bugs.kde.org/show_bug.cgi?id=386811
Roman Gilg <subd...@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |subd...@gmail.com --- Comment #3 from Roman Gilg <subd...@gmail.com> --- There is currently a rewrite of the mouse/input kcm happening to put it on par with the touchpad KCM in Wayland: https://phabricator.kde.org/D8168 That means: In Wayland session using libinput directly to change mouse speed / acceleration profile. Currently the mouse speed (or is it the acceleration?) on KWin Wayland is controlled via a hack by the same value as for X. There is some difficulty for me to grasp on how Windows, X and libinput each define speed, acceleration and acceleration profile (and threshold on X). So I'm not sure that in the end how libinput will handle it is what you're asking for in this bug report. Maybe you can clear this up? See here for how libinput doc describes the terminology: https://wayland.freedesktop.org/libinput/doc/latest/pointer-acceleration.html Note also that Martin for sure wasn't trying to be insulting to you. He probably just has the same difficulties as myself to understand what's the difference between libinput's acceleration vs. acceleration profile vs. speed. Closing the issue doesn't mean your feedback is dismissed. After we understand (with your help) the problem more properly we can reopen the issue at any time. So please reply, if the rewrite of the input kcm with libinput would already solve your issue or if it is something else. I believe gamers normally want to have something like - in Windows terminology - "0 acceleration" (in libinput/X terminology: a flat profile) and only change the overall mouse cursor - in Windows terminology - "speed" (in libinput terminology: acceleration). So the rewrite might just be what you're asking for here. -- You are receiving this mail because: You are watching all bug changes.