quirks: disable debouncing on the VMware Virtual mice

At least on MacBooks, the host emulates two clicks 8ms apart in response to a
doubletap. Those clicks are filtered by our debouncing code.

Since these are emulated devices anyway and by definition cannot have a stuck
button, let's tag them so we don't enable the debouncing code. If the button
of the physical device is stuck, that's a problem that needs to be fixed in
the host system.

Fixes #158

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
This commit is contained in:
Peter Hutterer 2018-10-11 10:21:54 +10:00
parent e96904e906
commit ec5d7702ff
3 changed files with 12 additions and 1 deletions

View file

@ -261,6 +261,7 @@ quirks_data = [
'quirks/30-vendor-razer.quirks',
'quirks/30-vendor-synaptics.quirks',
'quirks/30-vendor-wacom.quirks',
'quirks/30-vendor-vmware.quirks',
'quirks/50-system-acer.quirks',
'quirks/50-system-apple.quirks',
'quirks/50-system-asus.quirks',

View file

@ -0,0 +1,10 @@
# Do not edit this file, it will be overwritten on update
[VMWare Virtual PS/2 Mouse]
MatchName=*VirtualPS/2 VMware VMMouse*
ModelBouncingKeys=1
[VMware VMware Virtual USB Mouse]
MatchName=*VMware VMware Virtual USB Mouse*
ModelBouncingKeys=1

View file

@ -95,7 +95,7 @@ static int events[] = {
TEST_DEVICE("vmware-virtmouse",
.type = LITEST_VMWARE_VIRTMOUSE,
.features = LITEST_WHEEL | LITEST_BUTTON | LITEST_ABSOLUTE,
.features = LITEST_WHEEL | LITEST_BUTTON | LITEST_ABSOLUTE | LITEST_NO_DEBOUNCE,
.interface = &interface,
.name = "VMware VMware Virtual USB Mouse",