Bug 360108 - Angle for circular scrolling on touchpad interpreted differently than in kde4 (conversion deg > rad missing)
Summary: Angle for circular scrolling on touchpad interpreted differently than in kde4...
Status: RESOLVED DUPLICATE of bug 359460
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_mouse (show other bugs)
Version: 5.5.5
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-05 10:25 UTC by Thomas Mitterfellner
Modified: 2016-07-18 21:11 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Mitterfellner 2016-03-05 10:25:50 UTC
The angle for circular scrolling is shown to be in degrees in the control module (and is written as-is to the synclient), however, the mouse-over text says it's in radians.
This results in virtually non-working circular scrolling when I enter the values I was used to from kde4. E.g. I had 5.76° there (quite sensitive), but when I set this in plasma 5, I had to make a lot of turns for the scrolling to move a tiny bit.
So essentially, the conversion between degree and radian is missing.

Reproducible: Always
Comment 1 Thomas Mitterfellner 2016-03-05 11:41:58 UTC
I just found that this is a duplicate of https://bugs.kde.org/show_bug.cgi?id=359460. I could not work around this by putting a script which calls synclient VertScrollDelta=106 into .config/plasma-workspace/env. I would be really glad if this could be fixed quickly as it makes two-finger and circular scrolling almost unusable/unconfigurable.
Comment 2 Thomas Mitterfellner 2016-03-06 15:30:30 UTC
I figured out a workaround now. I put a setscroll.desktop file into ~/.config/autostart which calls a script which executes 
synclient VertScrollDelta=106
synclient HorizScrollDelta=106
Comment 3 Christoph Feck 2016-07-18 21:11:23 UTC
If the fix for bug 359460 did not fix this issue, please add a comment.

*** This bug has been marked as a duplicate of bug 359460 ***