| 1 |
:orphan: |
| 2 |
|
| 3 |
.. _touchpads: |
| 4 |
|
| 5 |
============================================================================== |
| 6 |
Touchpads |
| 7 |
============================================================================== |
| 8 |
|
| 9 |
This page provides an outline of touchpad devices. Touchpads aren't simply |
| 10 |
categorised into a single type, instead they have a set of properties, a |
| 11 |
combination of number of physical buttons, multitouch support abilities and |
| 12 |
other properties. |
| 13 |
|
| 14 |
.. _touchpads_buttons: |
| 15 |
|
| 16 |
------------------------------------------------------------------------------ |
| 17 |
Number of buttons |
| 18 |
------------------------------------------------------------------------------ |
| 19 |
|
| 20 |
.. _touchpads_buttons_phys: |
| 21 |
|
| 22 |
.............................................................................. |
| 23 |
Physically separate buttons |
| 24 |
.............................................................................. |
| 25 |
|
| 26 |
Touchpads with physical buttons usually provide two buttons, left and right. |
| 27 |
A few touchpads with three buttons exist, and Apple used to have touchpads |
| 28 |
with a single physical buttons until ca 2008. Touchpads with only two |
| 29 |
buttons require the software stack to emulate a middle button. libinput does |
| 30 |
this when both buttons are pressed simultaneously. |
| 31 |
|
| 32 |
Note that many Lenovo laptops provide a pointing stick above the touchpad. |
| 33 |
This pointing stick has a set of physical buttons just above the touchpad. |
| 34 |
While many users use those as substitute touchpad buttons, they logically |
| 35 |
belong to the pointing stick. The \*40 and \*50 series are an exception here, |
| 36 |
the former had no physical buttons on the touchpad and required the top |
| 37 |
section of the pad to emulate pointing stick buttons, the \*50 series has |
| 38 |
physical buttons but they are wired to the touchpads. The kernel re-routes |
| 39 |
those buttons through the trackstick device. See :ref:`t440_support` for more |
| 40 |
information. |
| 41 |
|
| 42 |
.. _touchpads_buttons_clickpads: |
| 43 |
|
| 44 |
.............................................................................. |
| 45 |
Clickpads |
| 46 |
.............................................................................. |
| 47 |
|
| 48 |
Clickpads are the most common type of touchpads these days. A Clickpad has |
| 49 |
no separate physical buttons, instead the touchpad itself is clickable as a |
| 50 |
whole, i.e. a user presses down on the touch area and triggers a physical |
| 51 |
click. Clickpads thus only provide a single button, everything else needs to |
| 52 |
be software-emulated. See :ref:`clickpad_softbuttons` for more information. |
| 53 |
|
| 54 |
Clickpads are labelled by the kernel with the **INPUT_PROP_BUTTONPAD** input |
| 55 |
property. |
| 56 |
|
| 57 |
.. _touchpads_buttons_forcepads: |
| 58 |
|
| 59 |
.............................................................................. |
| 60 |
Forcepads/Pressurepads |
| 61 |
.............................................................................. |
| 62 |
|
| 63 |
Forcepads are Clickpads without a physical button underneath the hardware. |
| 64 |
They provide pressure and may have a vibration element that is |
| 65 |
software-controlled. This element can simulate the feel of a physical |
| 66 |
click or be co-opted for other tasks. |
| 67 |
|
| 68 |
Forcepads are also called pressurepads or haptic touchpads. |
| 69 |
|
| 70 |
.. _touchpads_touch: |
| 71 |
|
| 72 |
------------------------------------------------------------------------------ |
| 73 |
Touch capabilities |
| 74 |
------------------------------------------------------------------------------ |
| 75 |
|
| 76 |
Virtually all touchpads available now can **detect** multiple fingers on |
| 77 |
the touchpad, i.e. provide information on how many fingers are on the |
| 78 |
touchpad. The touch capabilities described here specify how many fingers a |
| 79 |
device can **track**, i.e. provide reliable positional information for. |
| 80 |
In the kernel each finger is tracked in a so-called "slot", the number of |
| 81 |
slots thus equals the number of simultaneous touches a device can track. |
| 82 |
|
| 83 |
.. _touchpads_touch_st: |
| 84 |
|
| 85 |
.............................................................................. |
| 86 |
Single-touch touchpads |
| 87 |
.............................................................................. |
| 88 |
|
| 89 |
Single-finger touchpads can track a single touchpoint. Most single-touch |
| 90 |
touchpads can also detect three fingers on the touchpad, but no positional |
| 91 |
information is provided for those. In libinput, these touches are termed |
| 92 |
"fake touches". The kernel sends **BTN_TOOL_DOUBLETAP**, |
| 93 |
**BTN_TOOL_TRIPLETAP**, **BTN_TOOL_QUADTAP** and **BTN_TOOL_QUINTTAP** |
| 94 |
events when multiple fingers are detected. |
| 95 |
|
| 96 |
.. _touchpads_touch_mt: |
| 97 |
|
| 98 |
.............................................................................. |
| 99 |
Pure multi-touch touchpads |
| 100 |
.............................................................................. |
| 101 |
|
| 102 |
Pure multi-touch touchpads are those that can track, i.e. identify the |
| 103 |
location of all fingers on the touchpad. Apple's touchpads support 16 |
| 104 |
touches, others support 5 touches like the Synaptics touchpads when using |
| 105 |
SMBus. |
| 106 |
|
| 107 |
These touchpads usually also provide extra information. Apple touchpads |
| 108 |
provide an ellipse and the orientation of the ellipse for each touch point. |
| 109 |
Other touchpads provide a pressure value for each touch point (see |
| 110 |
:ref:`touchpads_pressure_handling`). |
| 111 |
|
| 112 |
Note that the kernel sends **BTN_TOOL_DOUBLETAP**, |
| 113 |
**BTN_TOOL_TRIPLETAP**, **BTN_TOOL_QUADTAP** and **BTN_TOOL_QUINTTAP** |
| 114 |
events for all touches for backwards compatibility. libinput ignores these |
| 115 |
events if the touchpad can track touches correctly. |
| 116 |
|
| 117 |
.. _touchpads_touch_partial_mt: |
| 118 |
|
| 119 |
.............................................................................. |
| 120 |
Partial multi-touch touchpads |
| 121 |
.............................................................................. |
| 122 |
|
| 123 |
The vast majority of touchpads fall into this category, the half-way |
| 124 |
point between single-touch and pure multi-touch. These devices can track N |
| 125 |
fingers, but detect more than N. For example, when using the serial |
| 126 |
protocol, Synaptics touchpads can track two fingers but may detect up to |
| 127 |
five. |
| 128 |
|
| 129 |
The number of slots may limit which features are available in libinput. |
| 130 |
Any device with two slots can support two-finger scrolling, but |
| 131 |
:ref:`thumb-detection` or :ref:`palm_detection` may be limited if only two |
| 132 |
slots are available. |
| 133 |
|
| 134 |
.. _touchpads_touch_semi_mt: |
| 135 |
|
| 136 |
.............................................................................. |
| 137 |
Semi-mt touchpads |
| 138 |
.............................................................................. |
| 139 |
|
| 140 |
A sub-class of partial multi-touch touchpads. These touchpads can |
| 141 |
technically detect two fingers but the location of both is limited to the |
| 142 |
bounding box, i.e. the first touch is always the top-left one and the second |
| 143 |
touch is the bottom-right one. Coordinates jump around as fingers move past |
| 144 |
each other. |
| 145 |
|
| 146 |
Many semi-mt touchpads also have a lower resolution for the second touch, or |
| 147 |
both touches. This may limit some features such as :ref:`gestures` or |
| 148 |
:ref:`scrolling`. |
| 149 |
|
| 150 |
Semi-mt are labelled by the kernel with the **INPUT_PROP_SEMI_MT** input |
| 151 |
property. |
| 152 |
|
| 153 |
.. _touchpads_mis: |
| 154 |
|
| 155 |
------------------------------------------------------------------------------ |
| 156 |
Other touchpad properties |
| 157 |
------------------------------------------------------------------------------ |
| 158 |
|
| 159 |
.. _touchpads_external: |
| 160 |
|
| 161 |
.............................................................................. |
| 162 |
External touchpads |
| 163 |
.............................................................................. |
| 164 |
|
| 165 |
External touchpads are USB or Bluetooth touchpads not in a laptop chassis, |
| 166 |
e.g. Apple Magic Trackpad or the Logitech T650. These are usually |
| 167 |
:ref:`touchpads_buttons_clickpads` the biggest difference is that they can be |
| 168 |
removed or added at runtime. |
| 169 |
|
| 170 |
One interaction method that is only possible on external touchpads is a |
| 171 |
thumb resting on the very edge/immediately next to the touchpad. On the far |
| 172 |
edge, touchpads don't always detect the finger location so clicking with a |
| 173 |
thumb barely touching the edge makes it hard or impossible to figure out |
| 174 |
which software button area the finger is on. |
| 175 |
|
| 176 |
These touchpads also don't need :ref:`palm_detection` - since they're not |
| 177 |
located underneath the keyboard, accidental palm touches are a non-issue. |
| 178 |
|
| 179 |
.. _touchpads_pressure_handling: |
| 180 |
|
| 181 |
.............................................................................. |
| 182 |
Touchpads pressure handling |
| 183 |
.............................................................................. |
| 184 |
|
| 185 |
Pressure is usually directly related to contact area. Human fingers flatten |
| 186 |
out as the pressure on the pad increases, resulting in a bigger contact area |
| 187 |
and the firmware then calculates that back into a pressure reading. |
| 188 |
|
| 189 |
libinput uses pressure to detect accidental palm contact and thumbs, though |
| 190 |
pressure data is often device-specific and unreliable. |
| 191 |
|
| 192 |
.. _touchpads_circular: |
| 193 |
|
| 194 |
.............................................................................. |
| 195 |
Circular touchpads |
| 196 |
.............................................................................. |
| 197 |
|
| 198 |
Only listed for completeness, circular touchpads have not been used in |
| 199 |
laptops for a number of years. These touchpad shaped in an ellipse or |
| 200 |
straight. |
| 201 |
|
| 202 |
.. _touchpads_tablets: |
| 203 |
|
| 204 |
.............................................................................. |
| 205 |
Graphics tablets |
| 206 |
.............................................................................. |
| 207 |
|
| 208 |
Touch-capable graphics tablets are effectively external touchpads, with two |
| 209 |
differentiators: they are larger than normal touchpads and they have no |
| 210 |
regular touchpad buttons. They either work like a |
| 211 |
:ref:`touchpads_buttons_forcepads` Forcepad, or rely on interaction methods that |
| 212 |
don't require buttons (like :ref:`tapping`). Since the physical device is |
| 213 |
shared with the pen input, some touch arbitration is required to avoid touch |
| 214 |
input interfering when the pen is in use. |
| 215 |
|
| 216 |
.. _touchpads_edge_zone: |
| 217 |
|
| 218 |
.............................................................................. |
| 219 |
Dedicated edge scroll area |
| 220 |
.............................................................................. |
| 221 |
|
| 222 |
Before :ref:`twofinger_scrolling` became the default scroll method, some |
| 223 |
touchpads provided a marking on the touch area that designates the |
| 224 |
edge to be used for scrolling. A finger movement in that edge zone should |
| 225 |
trigger vertical motions. Some touchpads had markers for a horizontal |
| 226 |
scroll area too at the bottom of the touchpad. |