[Wayland-bugs] [Bug 99914] Combined Keyboard+Mouse+Touchpad device problems

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=99914

--- Comment #8 from Peter Hutterer <peter.hutterer at who-t.net> ---
(In reply to Gergely Nagy from comment #6)
> Some more data points: I've been staring at xf86-input-libinput, and noticed
> that it sets the axis max to 0xffff for absolute devices.

yes, that's a side-effect of the xserver design, we need to have the full axis
range, but libinput doesn't provide that one ahead of time. So we just map to a
range of [0, 0xffff] instead and transform the coordinates to that (see
xf86libinput_handle_absmotion). There shouldn't be a scaling bug since it works
for libinput directly. The real problem is likely that the device gets set up
as relative device and then the server gets confused when you send absolute
events. I don't know off-heart what the server uses for scaling in that case.

Either way, a few well-placed ErrorF() should help (works like printf)

> so perhaps the
> problem is being on the same node and/or not having the BTN_TOUCH_* flags?

if it is just an absolute pointing device and not a real touchpad, you
shouldn't have BTN_TOUCH or BTN_TOOL_FINGER, so you're good there. But having
real+abs on one node just wont' work (yet) because of xf86-input-libinput
limitations.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/wayland-bugs/attachments/20170223/b4a6cf12/attachment.html>