touch-packages team mailing list archive

[Daniel van Vugt <daniel.van.vugt@xxxxxxxxxxxxx>]

mir (0.16.0+15.10.20150921.1-0ubuntu1) wily; urgency=medium


** Also affects: mir (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: mir (Ubuntu)
   Importance: Undecided => Medium

** Changed in: mir (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1496814

Title:
  touchpad produces mouse events with zeroed relative_x and relative_y
  axes

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  If you move the mouse pointer using a touch pad, the mouse events
  produced always have mir_pointer_axis_relative_x=0 and
  mir_pointer_axis_relative_y=0.

  Using mir 0.15.1 in wily

  This is probably because the InputMapper in (InputReader.cpp) for
  Touchpads is different from the mouse cursor event mapper. Currently
  relative_x and relative_y is evaluated there... it might be better to
  evaluate it at a higher level. Or add position tracking code to the
  touch pad input mapper.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1496814/+subscriptions