Peek at the ABS_MT_SLOT-1 axis. Expect that touch screens only
have axes inside the MT range.
---
src/udev/udev-builtin-input_id.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/udev/udev-builtin-input_id.c b/src/udev/udev-builtin-input_id.c
index 0f9f021..59616c8
Peek at the ABS_MT_SLOT-1 axis. Expect that touch screens only
have axes inside the MT range.
---
src/udev/udev-builtin-input_id.c | 4
1 file changed, 4 insertions(+)
diff --git a/src/udev/udev-builtin-input_id.c b/src/udev/udev-builtin-input_id.c
index 0f9f021..7fa7d1a 100644
---
Hi,
On Fri, May 29, 2015 at 2:07 AM, Peter Hutterer peter.hutte...@who-t.net
wrote:
On Thu, May 28, 2015 at 02:47:35PM +0200, Andreas Pokorny wrote:
There are touch screens that do not provide 'BTN_TOUCH' and hence no
'EV_KEY'. Previously those would not get any properties assigned
.
regards
Andreas Pokorny
Andreas Pokorny (3):
udev: input_id - refactor device detection
udev: input_id - use direct property and mt axis for touch screen
detection
udev: input_id - use ABS_MT_SLOT{-1} to exclude non touch screen
devices
src/udev/udev-builtin-input_id.c | 141
This change switches to bools and separates bit flag evaluation from
decision making and application of udev properties, while hopefully
keeping the same semantics. Apart from using BTN_LEFT instead of BTN_MOUSE
for mouse detection.
---
src/udev/udev-builtin-input_id.c | 134
Require touch screens to have a ABS_MT_SLOT axis while exclude devices
that overlap with the MT range of axes.
---
src/udev/udev-builtin-input_id.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/src/udev/udev-builtin-input_id.c b/src/udev/udev-builtin-input_id.c
index
A lot of touch screens use INPUT_PROP_DIRECT to indicate that touch input
maps directly to the underlying screen, while the BTN_TOUCH bit might not be
set.
---
src/udev/udev-builtin-input_id.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git
There are touch screens that do not provide 'BTN_TOUCH' and hence no
'EV_KEY'. Previously those would not get any properties assigned and
libinput would not treat those as input devices. Additionally there
is an 'IS_DIRECT' property exposed by most touch screens, that would
otherwise be detected
There are touch screens that do not provide 'BTN_TOUCH' and hence no
'EV_KEY'. Previously those would not get any properties assigned and
libinput would not treat those as input devices. Additionally there
is an 'IS_DIRECT' property exposed by most touch screens, that would
otherwise be detected
