There isn't one. Trying to use a touchscreen to run regular desktop
linux has major usability problems, as I'm sure you've noticed!
My point is there is no mystery bug or hardware problem that's going to
be solved by looking in logs. evdev's buttom emulation only works for
touch pads, not touch
There really isn't any mystery here. 3 button emulation only works for
BUTTON events. This touchscreen generates TOUCH events. It's totally
different kind of event than a mouse button getting clicked. 3 button
emu doesn't exist for touch events.
--
You received this bug notification because y
Upon looking at the code in evdev, it's clear the third button emulation
is completely non-functional for multitouch devices.
The emulation is triggered by calling Evdev3BEmuFilterEvent() from
EvdevPostQueuedEvents() in evdev.c. This is done for events of type
EV_QUEUE_BTN only. With a multitouc
The problem with the coordinate transform matrix not working is solved
by this patch: http://patchwork.freedesktop.org/patch/12471/
These touchscreens sometimes only send one axis if the other axis hasn't
changed. The server would take the new untransformed X axis sent by the
screen and the saved
Found out something new. I compiled the git version of evdev, xf86
-input-evdev-2.7.0-20-g5af11b6, and when multitouch isn't enabled, the
core state problem is gone. The autoconf script doesn't detect XI22 on
Precise because the X.org version is too old, so MT isn't enabled by
default.
Once I m
I see this same behavior on a Samsung Slate 7, which has an Atmel
maxtouch multitouch touchscreen. Running Precise, with xserver-xorg-
input-evdev 1:2.7.0-0ubuntu1.2 and xserver-xorg-core
2:1.11.4-0ubuntu10.8.
If I don't touch the touchscreen since the X server has started, xev
reports the state
