| Summary: | tap-to-click not enabled in plasma by default | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Frank Griffin <ftg> |
| Component: | RPM Packages | Assignee: | Nicolas Lécureuil <mageia> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | balcaen.john, marja11 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | task-plasma | CVE: | |
| Status comment: | |||
|
Description
Frank Griffin
2015-09-02 14:50:52 CEST
(In reply to Frank Griffin from comment #0) > Just as it says. First GNOME, now Plasma ? Since when did tap-to-click > become a pariah ? Why would any touchpad user *not* want this enabled ? > When there are buttons to click with and a pad too easily thinks that it's tapped when it isn't? I don't care what the default is, though, was just trying to think of a reason to disable "tap-to-click" ;-) CC:
(none) =>
balcaen.john, lmenut, marja11 :-) Well, if there actually are any such touchpad luddites, I'm sure they're in a small minority. I was just wondering if there was some crusade in the greater Linux community that was pushing for this. To GNOME and Plasma, you can add GDM and our own installer (gtk3). The desktops aren't a problem, as you can simply turn it back on (I hope). The problem is stuff like the installer and DMs, since it's not configurable there. With the install in particular, this has happened before, I've reported it, and it's been fixed. When it breaks, it leads to a barrage of bug reports saying that "MGA doesn't support my touchpad" because virtually every touchpad user expects it to work, and if it doesn't on their first interaction with MGA, they're not going to stick around. Ping ?
Luc Menut
2015-11-05 08:44:01 CET
CC:
lmenut =>
(none) |