lp:~aacid/qtmir/drag_and_drop

Branch merges

On hold for merging into lp:qtmir

Mir development team: Pending requested 2017-03-31

Unity8 CI Bot: Pending (continuous-integration) requested 2017-03-31

Diff: 74 lines (+21/-1)

3 files modified

src/platforms/mirserver/eventbuilder.cpp (+2/-0)
src/platforms/mirserver/windowmanagementpolicy.cpp (+14/-0)
src/platforms/mirserver/windowmanagementpolicy.h (+5/-1)

api

Propose for merging

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

632. By Albert Astals Cid on 2017-03-31

Merge

631. By Albert Astals Cid on 2017-03-30

Merge lp:~aacid/qtmir/dont_reuse_stale_cookies

630. By Albert Astals Cid on 2017-03-28

Implement handle_request_drag_and_drop

629. By Albert Astals Cid on 2017-03-28

Merge lp:~andreas-pokorny/qtmir/keep-mir-types-alive

628. By Alan Griffiths on 2017-03-24

Remove comment out

627. By Alan Griffiths on 2017-03-24

Fix build errors against lp:mir

626. By Alan Griffiths on 2017-03-24

merge lp:~alan-griffiths/qtmir/future-proof

625. By CI Train Bot Account on 2017-03-20

Releasing 0.5.1+17.04.20170320.1-0ubuntu1

624. By Andreas Pokorny on 2017-03-20

Attach MirInputDeviceId and the MirCookie to input events

Similar to the tracking of relative motion the cookie and input device ids of mir events are stored in the EventBuilder for later recovery (LP: #1536279, #1668692)

Approved by: Daniel d'Andrada, Unity8 CI Bot

623. By Gerry Boland on 2017-03-20

Extend timeouts when running under valgrind

When QMirServer is starting up, it spawns a separate thread for Mir to startup and waits for it. As valgrind slows execution greatly, the QMirServer timeout triggers before Mir has started, causing the QMirServer to think it failed and exit.

This patch adds ability to detect when running under valgrind and extending timeouts to suit.

Approved by: Daniel d'Andrada, Unity8 CI Bot