<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Combined Keyboard+Mouse+Touchpad device problems" href="https://bugs.freedesktop.org/show_bug.cgi?id=99914#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Combined Keyboard+Mouse+Touchpad device problems" href="https://bugs.freedesktop.org/show_bug.cgi?id=99914">bug 99914</a> from <a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> Peter Hutterer</a> <pre>(In reply to Gergely Nagy from <a href="show_bug.cgi?id=99914#c6">comment #6</a>) > 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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>