libinput/doc/page-hierarchy.dox
Peter Hutterer 55d1bb1217 pointer: add button debouncing
Some devices have worn-out switches or just cheap switches that trigger
multiple button events for each press. These can be identified by unfeasably
short time deltas between the release and the next press event. In the
recordings I've seen so far, that timeout is 8ms.

We have a two-stage behavior: by default, we do not delay any events but we
monitor timestamps. The first time a bouncing button is detected we switch to
debounce mode. From then on, release events are delayed slightly to check for
subsequent button events. If one occurs, the releas and press are filtered. If
none occurs, the release event is passed to the caller.

https://bugs.freedesktop.org/show_bug.cgi?id=100057

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2017-07-26 00:21:46 +10:00

53 lines
1,002 B
Text

/**
@page touchpads Touchpads
- @subpage scrolling
- @subpage clickpad_softbuttons
- @subpage tapping
- @subpage gestures
- @subpage touchpad_pressure
- @subpage palm_detection
- @subpage t440_support
- @subpage touchpad_jumping_cursor
- @subpage absolute_coordinate_ranges
@page touchscreens Touchscreens
- @subpage absolute_axes
@page pointers Mice, Trackballs, etc.
- @subpage motion_normalization
- @subpage middle_button_emulation
- @subpage button_debouncing
@page tablets Graphics Tablets
- @subpage tablet-support
@page general General
- @subpage udev_config
- @subpage seats
- @subpage timestamps
@page misc Users
- @subpage what_is_libinput
- @subpage faq
- @subpage tools
- @subpage reporting_bugs
@page developers Developers
Contributions to libinput are always welcome. See the links below for
specific documentation.
- @subpage what_is_libinput
- @subpage contributing
- @subpage building_libinput
- @subpage test-suite
- @subpage tools
- @subpage pointer-acceleration
*/