When an absolute pointer motion event is handled in the drm backend, it's requested absolute x,y values are passed to notify_motion() and treated as a relative x,y values. For example, I have a test program that creates an absolute uinput pointer device. Weston detects the device correctly as: [18:34:57.184] input device MY UINPUT ABS POINTER, /dev/input/event10 is a pointer caps = absolute-motion button However, when my test program moves the absolute pointer to, say, x=200 y=100, Weston actually moves it to x=200+"current x" y=100+"current y". This is a regression since it was recently working fine... The first bad commit is http://cgit.freedesktop.org/wayland/weston/commit/?id=068b61c25488cb55c686142886d988f3d6554ec0
Created attachment 77111 [details] [review] compositor: Support notifying with absolute position too
Committed, thanks. commit c088e2c01145d05eddb3314de17c8dbec6b8cb62 Author: Rob Bradford <rob@linux.intel.com> Date: Wed Mar 27 15:59:43 2013 +0000 compositor: Support notifying with absolute position too With evdev input devices that generate absolute positions we need to provide an infrastructure in the compositor for supporting those. Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=61997
Thanks Rob!
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.