[Ubuntu-sdk-bugs] [Bug 1597205] Re: Not sending relative mouse events to clients
** Project changed: qtmir => qtmir (Ubuntu) -- 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: Fix Released Status in qtdeclarative-opensource-src package in Ubuntu: Fix Released Status in qtmir package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Invalid 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(qtEvent->timestamp())); auto modifiers = getMirModifiersFromQt(qtEvent->modifiers()); auto buttons = getMirButtonsFromQt(qtEvent->buttons()); return mir::events::make_event(0 /*DeviceID */, timestamp, std::vector{} /* 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 -- 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
[Ubuntu-sdk-bugs] [Bug 1597205] Re: Not sending relative mouse events to clients
** Changed in: qtmir 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: Fix Released Status in QtMir: Fix Released Status in qtdeclarative-opensource-src package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Invalid 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(qtEvent->timestamp())); auto modifiers = getMirModifiersFromQt(qtEvent->modifiers()); auto buttons = getMirButtonsFromQt(qtEvent->buttons()); return mir::events::make_event(0 /*DeviceID */, timestamp, std::vector{} /* 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 -- 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
[Ubuntu-sdk-bugs] [Bug 1597205] Re: Not sending relative mouse events to clients
** Changed in: canonical-devices-system-image Status: Fix Committed => 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: Fix Released Status in QtMir: In Progress Status in qtdeclarative-opensource-src package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Invalid 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(qtEvent->timestamp())); auto modifiers = getMirModifiersFromQt(qtEvent->modifiers()); auto buttons = getMirButtonsFromQt(qtEvent->buttons()); return mir::events::make_event(0 /*DeviceID */, timestamp, std::vector{} /* 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 -- 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
[Ubuntu-sdk-bugs] [Bug 1597205] Re: Not sending relative mouse events to clients
This bug was fixed in the package qtdeclarative-opensource-src - 5.6.1-4ubuntu2~1 --- qtdeclarative-opensource-src (5.6.1-4ubuntu2~1) yakkety; 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 Wed, 27 Jul 2016 12:11:13 + ** Changed in: qtdeclarative-opensource-src (Ubuntu) Status: Confirmed => 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: Fix Committed Status in QtMir: In Progress Status in qtdeclarative-opensource-src package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Invalid 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(qtEvent->timestamp())); auto modifiers = getMirModifiersFromQt(qtEvent->modifiers()); auto buttons = getMirButtonsFromQt(qtEvent->buttons()); return mir::events::make_event(0 /*DeviceID */, timestamp, std::vector{} /* 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 -- 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
[Ubuntu-sdk-bugs] [Bug 1597205] Re: Not sending relative mouse events to clients
** Changed in: unity8 (Ubuntu) Status: In Progress => Invalid -- 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: Fix Committed Status in QtMir: In Progress Status in qtdeclarative-opensource-src package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Invalid 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(qtEvent->timestamp())); auto modifiers = getMirModifiersFromQt(qtEvent->modifiers()); auto buttons = getMirButtonsFromQt(qtEvent->buttons()); return mir::events::make_event(0 /*DeviceID */, timestamp, std::vector{} /* 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 -- 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
[Ubuntu-sdk-bugs] [Bug 1597205] Re: Not sending relative mouse events to clients
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 Thu, 02 Jun 2016 10:18:08 + ** 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(qtEvent->timestamp())); auto modifiers = getMirModifiersFromQt(qtEvent->modifiers()); auto buttons = getMirButtonsFromQt(qtEvent->buttons()); return mir::events::make_event(0 /*DeviceID */, timestamp, std::vector{} /* 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 -- 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
[Ubuntu-sdk-bugs] [Bug 1597205] Re: Not sending relative mouse events to clients
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Milestone: None => 13 ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Zoltan Balogh (bzoltan) ** Changed in: canonical-devices-system-image 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 Canonical System Image: In Progress 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(qtEvent->timestamp())); auto modifiers = getMirModifiersFromQt(qtEvent->modifiers()); auto buttons = getMirButtonsFromQt(qtEvent->buttons()); return mir::events::make_event(0 /*DeviceID */, timestamp, std::vector{} /* 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 -- 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
[Ubuntu-sdk-bugs] [Bug 1597205] Re: Not sending relative mouse events to clients
** 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(qtEvent->timestamp())); auto modifiers = getMirModifiersFromQt(qtEvent->modifiers()); auto buttons = getMirButtonsFromQt(qtEvent->buttons()); return mir::events::make_event(0 /*DeviceID */, timestamp, std::vector{} /* 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
[Ubuntu-sdk-bugs] [Bug 1597205] Re: Not sending relative mouse events to clients
Need to backport https://codereview.qt-project.org/#/c/164552/ into qtdeclarative ** Also affects: qtdeclarative-opensource-src (Ubuntu) Importance: Undecided Status: New ** Changed in: qtdeclarative-opensource-src (Ubuntu) Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki) -- 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 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(qtEvent->timestamp())); auto modifiers = getMirModifiersFromQt(qtEvent->modifiers()); auto buttons = getMirButtonsFromQt(qtEvent->buttons()); return mir::events::make_event(0 /*DeviceID */, timestamp, std::vector{} /* 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