Merge lp:~dandrader/unity8/mirSurfaceInputBounds into lp:unity8
| Status: | Merged |
|---|---|
| Approved by: | Michael Zanetti on 2016-07-06 |
| Approved revision: | 2527 |
| Merged at revision: | 2543 |
| Proposed branch: | lp:~dandrader/unity8/mirSurfaceInputBounds |
| Merge into: | lp:unity8 |
| Diff against target: |
563 lines (+86/-186) (has conflicts) 17 files modified
CMakeLists.txt (+1/-1) debian/changelog (+9/-0) debian/control (+4/-3) qml/Components/InputMethod.qml (+8/-44) qml/Shell.qml (+1/-1) qml/Stages/DesktopStage.qml (+5/-1) tests/mocks/Unity/Application/CMakeLists.txt (+0/-1) tests/mocks/Unity/Application/MirSurface.cpp (+21/-0) tests/mocks/Unity/Application/MirSurface.h (+8/-0) tests/mocks/Unity/Application/UbuntuKeyboardInfo.cpp (+0/-58) tests/mocks/Unity/Application/UbuntuKeyboardInfo.h (+0/-57) tests/mocks/Unity/Application/VirtualKeyboard.cpp (+20/-1) tests/mocks/Unity/Application/VirtualKeyboard.h (+4/-1) tests/mocks/Unity/Application/plugin.cpp (+0/-8) tests/mocks/Unity/Application/resources/VirtualKeyboard.qml (+1/-6) tests/qmltests/Stages/tst_DesktopStage.qml (+3/-3) tests/qmltests/Tutorial/tst_Tutorial.qml (+1/-1) Text conflict in debian/changelog |
| To merge this branch: | bzr merge lp:~dandrader/unity8/mirSurfaceInputBounds |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Lukáš Tinkl (community) | 2016-06-30 | Needs Fixing on 2016-07-18 | |
| Michał Sawicz | packaging | Approve on 2016-07-12 | |
| Unity8 CI Bot | continuous-integration | 2016-06-30 | Needs Fixing on 2016-07-06 |
| Michael Zanetti (community) | 2016-06-30 | Approve on 2016-07-06 | |
|
Review via email:
|
|||
This proposal supersedes a proposal from 2016-06-29.
Commit Message
Make use of MirSurface:
Description of the Change
All packages are in this silo: https:/
* Are there any related MPs required for this MP to build/function as expected? Please list.
https:/
https:/
https:/
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?
Not applicable
* If you changed the UI, has there been a design review?
Not applicable
| Albert Astals Cid (aacid) wrote : | # |
Text conflict in debian/control
1 conflicts encountered.
| Daniel d'Andrada (dandrader) wrote : | # |
On 20/06/2016 04:24, Albert Astals Cid wrote:
> Text conflict in debian/control
> 1 conflicts encountered.
>
Fixed.
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2491
https:/
Executed test runs:
FAILURE: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
Click here to trigger a rebuild:
https:/
| Albert Astals Cid (aacid) wrote : | # |
Contents conflict in tests/mocks/
1 conflicts encountered.
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2526
https:/
Executed test runs:
FAILURE: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
Click here to trigger a rebuild:
https:/
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2527
https:/
Executed test runs:
FAILURE: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
Click here to trigger a rebuild:
https:/
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2531
https:/
Executed test runs:
FAILURE: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
Click here to trigger a rebuild:
https:/
| Michael Zanetti (mzanetti) wrote : | # |
This moves all windows up when the OSK is shown. Should only move the focused one instead
| Michael Zanetti (mzanetti) wrote : | # |
not sure if it's a good idea to change that away from appContainer. The appContainer might be moved around depending on other factors (launcher shown etc). Apart from the previously mentioned breakage in maximizing, this is probably gonna make things harder if we need to consider the appContainer *and* the visibleRect in the future... I would probably prefer that you don't refactor this stuff too much. Not only because this is conflicting already a lot with the unified staged stuff...
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2526
https:/
Executed test runs:
FAILURE: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
Click here to trigger a rebuild:
https:/
| Michael Zanetti (mzanetti) wrote : | # |
Code looks ok. Thanks for reverting the refactor. As discussed on IRC, lets see how to get that in when the stages are merged. The issues with the window displacement are fixed now too.
However, for some reason this seems to break the OSK for apps when it is on the external screen (Tested with frieza plugged to a external HDMI screen). Text fields can't get focused any more. Could well be that it's not this branch, but instead another one from the silo. Can you please verify that?
| Daniel d'Andrada (dandrader) wrote : | # |
On 04/07/2016 13:40, Michael Zanetti wrote:
> However, for some reason this seems to break the OSK for apps when it is on the external screen (Tested with frieza plugged to a external HDMI screen). Text fields can't get focused any more. Could well be that it's not this branch, but instead another one from the silo. Can you please verify that?
Reproduced with mako.
| Daniel d'Andrada (dandrader) wrote : | # |
> Code looks ok. Thanks for reverting the refactor. As discussed on IRC, lets
> see how to get that in when the stages are merged. The issues with the window
> displacement are fixed now too.
>
>
> However, for some reason this seems to break the OSK for apps when it is on
> the external screen (Tested with frieza plugged to a external HDMI screen).
> Text fields can't get focused any more. Could well be that it's not this
> branch, but instead another one from the silo. Can you please verify that?
Turns out to be a mir bug (https:/
Works fine now.
| Michał Sawicz (saviq) wrote : | # |
Text conflict in qml/Stages/
1 conflicts encountered.
- 2527. By Daniel d'Andrada on 2016-07-06
-
Merge trunk
[ Michael Zanetti ]
don't displace windows if the OSK is on another screen (LP:
#1598917)
| Daniel d'Andrada (dandrader) wrote : | # |
On 06/07/2016 09:30, Michał Sawicz wrote:
> Review: Needs Fixing
>
> Text conflict in qml/Stages/
> 1 conflicts encountered.
Fixed
| Unity8 CI Bot (unity8-ci-bot) wrote : | # |
FAILED: Continuous integration, rev:2527
https:/
Executed test runs:
FAILURE: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
Click here to trigger a rebuild:
https:/
- 2528. By Daniel d'Andrada on 2016-07-07
-
tst_Tutorial: Update test_oskDoesNot
HideTutorial - 2529. By Daniel d'Andrada on 2016-07-12
-
This new unity8 is not compatible with current/old ubuntu-keyboard
- 2530. By Daniel d'Andrada on 2016-07-12
-
Bump version
| Daniel d'Andrada (dandrader) wrote : | # |
> Text conflict in debian/changelog
I don't see any.

FAILED: Continuous integration, rev:2441 /unity8- jenkins. ubuntu. com/job/ lp-unity8- ci/1457/ /unity8- jenkins. ubuntu. com/job/ build/1937/ console /unity8- jenkins. ubuntu. com/job/ build-0- fetch/1963 /unity8- jenkins. ubuntu. com/job/ build-1- sourcepkg/ release= vivid+overlay/ 1898 /unity8- jenkins. ubuntu. com/job/ build-1- sourcepkg/ release= xenial+ overlay/ 1898 /unity8- jenkins. ubuntu. com/job/ build-1- sourcepkg/ release= yakkety/ 1898 /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=amd64, release= vivid+overlay/ 1889/console /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=amd64, release= xenial+ overlay/ 1889/console /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=amd64, release= yakkety/ 1889/console /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=armhf, release= vivid+overlay/ 1889/console /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=armhf, release= xenial+ overlay/ 1889/console /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=armhf, release= yakkety/ 1889/console /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=i386, release= vivid+overlay/ 1889/console /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=i386, release= xenial+ overlay/ 1889/console /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=i386, release= yakkety/ 1889/console
https:/
Executed test runs:
FAILURE: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
Click here to trigger a rebuild: /unity8- jenkins. ubuntu. com/job/ lp-unity8- ci/1457/ rebuild
https:/