ubuntu-sdk-bugs team mailing list archive
-
ubuntu-sdk-bugs team
-
Mailing list archive
-
Message #06945
[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>(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