diff options
Diffstat (limited to 'en/devices/input/touch-devices.html')
| -rw-r--r-- | en/devices/input/touch-devices.html | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/en/devices/input/touch-devices.html b/en/devices/input/touch-devices.html index 8cbcc66b..e3126ed8 100644 --- a/en/devices/input/touch-devices.html +++ b/en/devices/input/touch-devices.html @@ -226,7 +226,8 @@ and <code>MotionEvent.ACTION_HOVER_EXIT</code>.</p> detect the capabilities of the device.</p> <p>For example, if the device reports the <code>BTN_TOUCH</code> key code, the system will assume that <code>BTN_TOUCH</code> will always be used to indicate whether the tool is -actually touching the screen or is merely in range and hovering.</p> + actually touching the screen. Therefore, <code>BTN_TOUCH</code> should not be used to indicate + that the tool is merely in the range and hovering.</p> </li> <li> <p>Single-touch devices use the following Linux input events:</p> @@ -564,7 +565,7 @@ the characteristics of touches using device-specific units.</p> <p>For example, many touch devices measure the touch contact area using an internal device-specific scale, such as the total number of sensor nodes that were triggered by the touch. This raw size value would -not be meaningful applications because they would need to know about the +not be meaningful to applications because they would need to know about the physical size and other characteristics of the touch device sensor nodes.</p> <p>The system uses calibration parameters encoded in input device configuration files to decode, transform, and normalize the values reported by the touch |