ubuntu-sdk-bugs team mailing list archive

[Łukasz Zemczak <1597205@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package qtdeclarative-opensource-src
5.4.1-1ubuntu11~overlay9~1 in https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/stable-phone-overlay

---------------

qtdeclarative-opensource-src (5.4.1-1ubuntu11~overlay9~1) vivid;
urgency=medium

  * debian/patches/Flickable-fix-minXExtent-minYExtent-when-content-is-.patch:
    - Fix flickable's widthRatio and heightRatio (LP: #1588238)
  * debian/patches/QQuickWindow-Fill-out-timestamps-in-QHoverEvents-sen.patch:
    - Fix relative mouse events (LP: #1597205)
    - debian/libqt5quick5.symbols: Update symbols.

 -- Timo Jyrinki <timo-jyrinki@xxxxxxxxxx>  Thu, 02 Jun 2016 10:18:08
+0000


** Changed in: qtdeclarative-opensource-src (Ubuntu RTM)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
SDK bug tracking, which is subscribed to qtdeclarative-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1597205

Title:
  Not sending relative mouse events to clients

Status in Canonical System Image:
  In Progress
Status in QtMir:
  In Progress
Status in qtdeclarative-opensource-src package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress
Status in qtdeclarative-opensource-src package in Ubuntu RTM:
  Fix Released

Bug description:
  QtMir is not sending relative mouse movements in mouse events.

  Relevant code from mirsurface.cpp:

  
  mir::EventUPtr makeMirEvent(QMouseEvent *qtEvent, MirPointerAction action)
  {
      auto timestamp = uncompressTimestamp<qtmir::Timestamp>(qtmir::Timestamp(qtEvent->timestamp()));
      auto modifiers = getMirModifiersFromQt(qtEvent->modifiers());
      auto buttons = getMirButtonsFromQt(qtEvent->buttons());

      return mir::events::make_event(0 /*DeviceID */, timestamp, std::vector<uint8_t>{} /* cookie */, modifiers, action,
                                     buttons, qtEvent->x(), qtEvent->y(), 0, 0, 0, 0);

  
  The last 2 parameters in the make_event call should be the relative x & y motion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1597205/+subscriptions