** Also affects: qtdeclarative-opensource-src (Ubuntu RTM) Importance: Undecided Status: New
** Changed in: qtdeclarative-opensource-src (Ubuntu RTM) Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki) ** Changed in: qtdeclarative-opensource-src (Ubuntu RTM) Importance: Undecided => High ** Changed in: qtdeclarative-opensource-src (Ubuntu) Importance: Undecided => High ** Changed in: qtdeclarative-opensource-src (Ubuntu RTM) Status: New => In Progress -- 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 QtMir: In Progress Status in qtdeclarative-opensource-src package in Ubuntu: New Status in unity8 package in Ubuntu: In Progress Status in qtdeclarative-opensource-src package in Ubuntu RTM: In Progress 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/qtmir/+bug/1597205/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-sdk-bugs Post to : ubuntu-sdk-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-sdk-bugs More help : https://help.launchpad.net/ListHelp