You are not logged in.
Is there a way to disable the physical "click" on the clickpad/touchpad of a laptop while you are typing? I know that syndaemon is able to disable taps and touches while typing, and I have even been able to get palm detection working, but I have not found a way to disable an actual physical click on clickpads. My palm will occasionally hit the touchpad while I am typing with enough force to "click" the clickpad and cause focus to change to a different application. This is the last annoyance I have to to resolve with my touchpad. Thanks!
Offline
Perhaps I am misunderstanding your hardware. I assume by physical click, you mean that you have a button that is separate from the touchpad. If this is the case (as it is on my laptop), then I don't know of much you can do with synclient/syndaemon. Sorry I couldn't be of more help.
A possible workaround is to set a key binding to disable/enable the appropriate click events. You can get the ID of your touchpad via
# xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ ETPS/2 Elantech Touchpad id=11 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Power Button id=8 [slave keyboard (3)]
↳ WebCam SC-13HDL11431N id=9 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)]Current mapping, change mapping to disable button 1, 2, and 3, and change mapping to re-enable buttons 1, 2, and 3
# xinput get-button-map 11
1 2 3 4 5 6 7 8 9 10 11 12
# xinput set-button-map 11 0 0 0
# xinput set-button-map 11 1 2 3I'd then set up key bindings (e.g. https://wiki.archlinux.org/index.php/Xbindkeys) to run the above commands to disable or enable the appropriate buttons whenever you are going to be typing for a while.
Offline
Maybe you could use something like https://bbs.archlinux.org/viewtopic.php?id=96610
Last edited by lucke (2014-09-17 01:30:40)
Offline
I have a System76 Galago Ultrapro. The touchpad/clickpad on this laptop is clickable. There are no buttons you click, the actual touchpad itself can be pressed and it physically moves down and clicks like a button (it also supports taps). Taps/touches are disabled by syndaemon but the physical click is not.
Offline
I have a System76 Galago Ultrapro. The touchpad/clickpad on this laptop is clickable. There are no buttons you click, the actual touchpad itself can be pressed and it physically moves down and clicks like a button (it also supports taps). Taps/touches are disabled by syndaemon but the physical click is not.
Because there is a button underneath it, so it has at least one button. Run:
xinput; # to determine ID
xinput list ID; # there should be a button listed
xinput test-ix2 ID; # to capture events@lucke This might be very handy, thank you.
Offline
xinput reports both a tap and a click as button 1. I'll look into the recommendations provided as they appear to be potential solutions for situations where I know I'll be typing for a while and not changing context. I was hoping for a solution that worked like syndaemon and would automatically disabled clicks when I start typing and re-enable them once I finish typing.
Offline
Look at what I linked to, it sets xinput one way when the keyboard is active and another way when it is inactive (see if IRQ 1 gets incremented in /proc/interrupts when you use the keyboard, it's how it detects keyboard activity). Set the xinput lines there the way you want them, save it, compile it with gcc, run it.
Offline
Now, if i understoand correctly, you accidently while typing click buttons on the touchpad?
I had this very problem and this is what i did and it solved the problem for me;
open the file /etc/X11/xorg.conf.d/50-synaptics.conf as root
in this file you will see among other things:
Section "InputClass"
Identifier "touchpad catchall"
Driver "synaptics"
MatchIsTouchpad "on"
Option "TapButton1" "1"
Option "TapButton2" "2"
Option "TapButton3" "3"
change it into this:
Section "InputClass"
Identifier "touchpad catchall"
Driver "synaptics"
MatchIsTouchpad "on"
# Option "TapButton1" "1"
# Option "TapButton2" "2"
# Option "TapButton3" "3"
hope i understodd your problem correctly and that this will help.
Offline