https://bugs.kde.org/show_bug.cgi?id=408051
Nate Graham changed:
What|Removed |Added
Version Fixed In||5.21
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=408051
Nate Graham changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=408051
David Edmundson changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/plas
https://bugs.kde.org/show_bug.cgi?id=408051
Bug Janitor Service changed:
What|Removed |Added
Status|CONFIRMED |ASSIGNED
--- Comment #8 from Bug Janitor
https://bugs.kde.org/show_bug.cgi?id=408051
Nate Graham changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=408051
Patrick Silva changed:
What|Removed |Added
CC||bugsefor...@gmx.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=408051
--- Comment #6 from Nate Graham ---
Ah, that's true.
We should indeed bring that back. However I would not put it in the mouse
settings, because it doesn't on;y affect mice (e.g. you duoble-click with a
touchpad too).
Maybe we need a combined "Mouse &
https://bugs.kde.org/show_bug.cgi?id=408051
--- Comment #5 from Christoph Feck ---
startDragDistance and related values are not input driver features, but Qt
features.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408051
--- Comment #4 from Nate Graham ---
It wasn't a QML port. Rather, a new QML UI was created to support using the
Libinput driver. The missing features are ones not supported by Libinput, not
anything that was missed or lost in the process of creating the
https://bugs.kde.org/show_bug.cgi?id=408051
--- Comment #3 from Christoph Feck ---
The startDragDistance used to be configurable with 'kcmshell5 mouse'.
Unfortunately the QML 'port' removed many options.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=408051
--- Comment #2 from Nate Graham ---
(In reply to Christoph Feck from comment #1)
> > a double-tap should not require that the cursor click the same spot
>
> Even for mouse clicks a slight tolerance should be accepted (pushing down
> the button can caus
https://bugs.kde.org/show_bug.cgi?id=408051
--- Comment #1 from Christoph Feck ---
> a double-tap should not require that the cursor click the same spot
Even for mouse clicks a slight tolerance should be accepted (pushing down the
button can cause a slight move). Some applications use the startD
12 matches
Mail list logo