After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 692772 - disable touchpad clicks only when typing
disable touchpad clicks only when typing
Status: RESOLVED DUPLICATE of bug 673055
Product: gnome-control-center
Classification: Core
Component: Mouse
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-01-29 08:58 UTC by Trevor Spiteri
Modified: 2013-01-29 09:06 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Trevor Spiteri 2013-01-29 08:58:26 UTC
I use the "Disable touchpad when typing" option to avoid spurious clicks during typing. But this disables moving the pointer as well. I don't think pointer motion should be disabled.


If I touch the touchpad by accident during typing, the pointer wouldn't move anyway, so there is no point in disabling pointer motion.

Exactly after typing, if I want to use the touchpad, I have to move the pointer first. So if pointer motion is not disabled, I save time (not a lot of time, but it is still frustrating if the computer breaks my flow).

The only downside I can think of is that if motion is enabled, there is no visual feedback to show that clicks are still disabled. But if I am dragging on the touchpad, it is pretty obvious that I want the touchpad enabled, so perhaps dragging on the touchpad for more than a tiny amount (which could be accidental) should reenable the touchpad immediately.
Comment 1 Bastien Nocera 2013-01-29 09:06:05 UTC
It was fixed in GNOME 3.6 released a couple of months ago.

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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