From c2c526a7c5287cf2c0beeff0cfbce66c51d79ce8 Mon Sep 17 00:00:00 2001 From: Peter Hutterer Date: Wed, 10 Feb 2016 14:13:10 +1000 Subject: [PATCH] doc: add a graphic illustrating pad vs tool support Signed-off-by: Peter Hutterer Reviewed-by: Jason Gerecke Reviewed-by: Carlos Garnacho --- doc/svg/tablet-interfaces.svg | 325 ++++++++++++++++++++++++++++++++++ doc/tablet-support.dox | 2 + 2 files changed, 327 insertions(+) create mode 100644 doc/svg/tablet-interfaces.svg diff --git a/doc/svg/tablet-interfaces.svg b/doc/svg/tablet-interfaces.svg new file mode 100644 index 00000000..d64fe9f3 --- /dev/null +++ b/doc/svg/tablet-interfaces.svg @@ -0,0 +1,325 @@ + + + + + + + + + + + + + + + + image/svg+xml + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Pad buttons + + Pad buttons + Pad buttons + Pad ring + + + + Pad ring + Tool buttons + + Tool tip + + + diff --git a/doc/tablet-support.dox b/doc/tablet-support.dox index 07de478b..0a44010b 100644 --- a/doc/tablet-support.dox +++ b/doc/tablet-support.dox @@ -23,6 +23,8 @@ Pad events do not require a tool to be in proximity. Note that both capabilities may exist on the same device though usually they are split across multiple kernel devices. +@image html tablet-interfaces.svg "Difference between Pad and Tool buttons" + Touch events on the tablet integrated into a screen itself are exposed through the @ref LIBINPUT_DEVICE_CAP_TOUCH capability. Touch events on a standalone tablet are exposed through the @ref LIBINPUT_DEVICE_CAP_POINTER