Merge lp://staging/~unity-team/qtmir/multimonitorNext into lp://staging/qtmir
Status: | Merged |
---|---|
Approved by: | Michał Sawicz |
Approved revision: | 390 |
Merged at revision: | 391 |
Proposed branch: | lp://staging/~unity-team/qtmir/multimonitorNext |
Merge into: | lp://staging/qtmir |
Prerequisite: | lp://staging/~unity-team/qtmir/surviveEmptyTexture |
Diff against target: |
345 lines (+77/-84) 11 files modified
src/common/debughelpers.cpp (+30/-1) src/common/debughelpers.h (+1/-0) src/platforms/mirserver/mirserver.cpp (+7/-1) src/platforms/mirserver/mirserverintegration.cpp (+3/-11) src/platforms/mirserver/qtcompositor.cpp (+13/-0) src/platforms/mirserver/qtcompositor.h (+12/-0) src/platforms/mirserver/qteventfeeder.cpp (+6/-2) src/platforms/mirserver/screencontroller.cpp (+5/-52) src/platforms/mirserver/screencontroller.h (+0/-1) src/platforms/mirserver/screenwindow.cpp (+0/-4) tests/mirserver/ScreenController/screencontroller_test.cpp (+0/-12) |
To merge this branch: | bzr merge lp://staging/~unity-team/qtmir/multimonitorNext |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Michał Sawicz | Approve | ||
Gerry Boland | Pending | ||
PS Jenkins bot | continuous-integration | Pending | |
Review via email: mp+274516@code.staging.launchpad.net |
This proposal supersedes a proposal from 2015-10-02.
Commit message
Improve multimonitor support
* Removed magic:
- Don't automagically select the screen where a window will be show.
Let shell decide.
- Don't automagically focus a window. Let shell handle it.
* Let shell know when a screen is about to be removed so that it has
the opportunity to move or destroy a window in it before it's too late.
- Added QGuiApplication
* Added logging to key events
Description of the change
Known issues:
- Input events come at very irregular intervals (if at all) when an external monitor is connected to a phone or tablet. Works fine on a laptop connected to an external monitor.
* Are there any related MPs required for this MP to build/function as expected? Please list.
No, but to see any difference you should use this untiy8 branch:
https:/
* Did you perform an exploratory manual test run of your code change and any related functionality?
Yes
* If you changed the packaging (debian), did you subscribe the ubuntu-unity team to this MP?
N/A
FAILED: Continuous integration, rev:387 jenkins. qa.ubuntu. com/job/ qtmir-ci/ 478/ jenkins. qa.ubuntu. com/job/ qtmir-vivid- amd64-ci/ 174/console jenkins. qa.ubuntu. com/job/ qtmir-vivid- armhf-ci/ 174/console jenkins. qa.ubuntu. com/job/ qtmir-vivid- i386-ci/ 56/console jenkins. qa.ubuntu. com/job/ qtmir-wily- amd64-ci/ 211/console jenkins. qa.ubuntu. com/job/ qtmir-wily- armhf-ci/ 211/console jenkins. qa.ubuntu. com/job/ qtmir-wily- i386-ci/ 56/console
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild: s-jenkins. ubuntu- ci:8080/ job/qtmir- ci/478/ rebuild
http://