[systemsettings] [Bug 372332] New: mouse kcm, advanced tab, pointer threshold minimum should be 0, not 1

[Duncan]

https://bugs.kde.org/show_bug.cgi?id=372332

            Bug ID: 372332
           Summary: mouse kcm, advanced tab, pointer threshold minimum
                    should be 0, not 1
           Product: systemsettings
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: kcm_mouse
          Assignee: unassigned-bugs at kde.org
          Reporter: 1i5t5.duncan at cox.net
                CC: unassigned-bugs at kde.org
  Target Milestone: ---

In the mouse kcm, on the advanced tab, for the pointer threshold setting...

The current minimum threshold is 1 pixel.  It should be 0 pixels.

The documentation I know of for this is the xset (1) manpage.  Under option
mouse (m), it says this about the threshold setting:

>>>>>

If the `threshold' parameter is provided and 0, the `acceleration' parameter
will be used in the exponent of a more natural and continuous formula, giving
precise control for slow motion but big reach for fast motion, and a
progressive transition for motions in between.  Recommended `acceleration'
value in this case is 3/2 to 3, but not limited to that range.

<<<<<

That's exactly what I wanted, so I had my threshold set to 0 here... until I
tried to adjust some other setting in the mouse kcm and set its minimum 1 px
threshold instead.  Now every time I restart kde/plasma I have a mouse that
appears to be stuck in molasses, and while I can xset m 31/10 0 to get the
speed back, it's back stuck in molasses when I restart kde again, because the 1
px minimum that plasma's mouse kcm sets apparently stuck! =:^(

And indeed, xset q reports 31/10 1.

So the mouse kcm needs to allow a 0 threshold, in ordered to enable people to
set the "natural and continuous formula" acceleration by setting a 0 threshold.

I guess I'll try to patch it myself, here, and will attach the patch here as
well, if I get to it before someone from plasma does.  Meanwhile, I suppose
I'll have to dig thru thru the config files to find that setting and manually
kill it, to get my 0 threshold "natural" acceleration formula back. =:^(

(I'm running KF5/plasma live-git.  kcmshell5 --version reports 5.8.90, ATM, but
that's not an available choice in the version field above... and chances are it
has had a 1 px minimum for some time, anyway, and I just got snared by it
today.)

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.