Merge lp:~aacid/unity8/pan_regression into lp:unity8
| Status: | Merged | ||||
|---|---|---|---|---|---|
| Approved by: | Andrea Cimitan on 2015-03-18 | ||||
| Approved revision: | 1667 | ||||
| Merged at revision: | 1693 | ||||
| Proposed branch: | lp:~aacid/unity8/pan_regression | ||||
| Merge into: | lp:unity8 | ||||
| Diff against target: |
73 lines (+22/-15) 3 files modified
qml/Components/ZoomableImage.qml (+14/-14) tests/qmltests/Components/tst_ZoomableImage.qml (+7/-0) tests/utils/modules/Unity/Test/UnityTestCase.qml (+1/-1) |
||||
| To merge this branch: | bzr merge lp:~aacid/unity8/pan_regression | ||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| PS Jenkins bot | continuous-integration | Needs Fixing on 2015-03-19 | |
| Andrea Cimitan (community) | 2015-03-18 | Approve on 2015-03-18 | |
|
Review via email:
|
|||
Commit Message
Fix regression making pan not possible in Zoomable Image
Qt never seems to send two presses standalone since that confuses code that still works on mouse events, the second one is always part of a move.
Also make the test check panning works so that it may be harder to regress again
Description of the Change
* Are there any related MPs required for this MP to build/function as expected?
No
* Did you perform an exploratory manual test run of your code change and any related functionality?
Yes
* Did you make sure that your branch does not contain spurious tags?
Yes
* If you changed the packaging (debian), did you subscribe the ubuntu-unity team to this MP?
N/A
* If you changed the UI, has there been a design review?
N/A
- 1667. By Albert Astals Cid on 2015-03-18
-
spacing
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1667
http://
Executed test runs:
UNSTABLE: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
| Andrea Cimitan (cimi) wrote : | # |
unrelated failures
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1667
http://
Executed test runs:
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://

* Did you perform an exploratory manual test run of the code change and any related functionality?
Yes
* Did CI run pass? If not, please explain why.
waiting
* Did you make sure that the branch does not contain spurious tags?
Yes