[Wayland-bugs] [Bug 61997] New: [regression] Absolute pointer motion values are treated as relative motion values on DRM backend

[bugzilla-daemon at freedesktop.org]

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

          Priority: medium
            Bug ID: 61997
          Assignee: wayland-bugs at lists.freedesktop.org
           Summary: [regression] Absolute pointer motion values are
                    treated as relative motion values on DRM backend
          Severity: critical
    Classification: Unclassified
                OS: All
          Reporter: ullysses.a.eoff at intel.com
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: weston
           Product: Wayland

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

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