On 06/21/2010 11:08 AM, Sascha Peilicke wrote:
On Monday 21 June 2010 17:56:19 Vincent Untz wrote:
Le lundi 21 juin 2010, à 17:07 +0200, Sascha Peilicke a écrit :
BTW. What was the rationale for disabling this anyway?
See my answer from earlier today: http://lists.opensuse.org/opensuse-factory/2010-06/msg00278.html
Quoting: =========== And my personal opinion (disabled by default) is based on seeing people getting confused when something clicks on the screen while they didn't press a button: it harms more the people who don't expect this behavior when it is enabled by default than the people who expect it when it is disabled by default. ===========
So people get confused when tapping on a touchpad creates a mouse click then? It does harm as this was the default for a long time and still is for the other distros out there. Also this creates other issues, like that <CTRL>+<Tap> to follow browser tabs don't work anymore. So this could be called a regression. There's a simple option for syndaemon that temporarily disables the touchpad while typing, isn't that actually what you want?
Sure, trying to make things simpler / more intuitive for new users is a good intend, but breaking the touchpad is not. Even less if that choice is only based on a sole decision.
It is not just a matter of getting confused. If you capacitance is wrong, and mine is, having tapping enabled can cause damage to the system. On a Netbook with Fedora 12 installed, the random clicks caused by just getting near the touchpad completely destroyed the desktop even though I was as careful as could be. The annoyance of not being able to tap is minor compared with the damage that random, unintended clicking can cause. Still, broken touchpad drivers should be the minority of cases for which kcm_touchpad or synaptiks can be used to turn the feature off simply. Forcing
On Monday 21 June 2010 18:23:26 you wrote: this on all others just because of some broken touchpads is not the solution. -- Sascha Peilicke http://saschpe.wordpress.com