Merge lp:~dandrader/unity8/floatingFlickable into lp:unity8
| Status: | Merged |
|---|---|
| Approved by: | Michael Zanetti on 2015-04-27 |
| Approved revision: | 1735 |
| Merged at revision: | 1779 |
| Proposed branch: | lp:~dandrader/unity8/floatingFlickable |
| Merge into: | lp:unity8 |
| Prerequisite: | lp:~dandrader/unity8/ddaImprovements |
| Diff against target: |
712 lines (+520/-32) 13 files modified
plugins/Ubuntu/Gestures/CMakeLists.txt (+1/-0) plugins/Ubuntu/Gestures/Direction.cpp (+6/-3) plugins/Ubuntu/Gestures/Direction.h (+3/-2) plugins/Ubuntu/Gestures/DirectionalDragArea.cpp (+3/-2) plugins/Ubuntu/Gestures/FloatingFlickable.cpp (+150/-0) plugins/Ubuntu/Gestures/FloatingFlickable.h (+86/-0) plugins/Ubuntu/Gestures/plugin.cpp (+3/-1) tests/plugins/Ubuntu/Gestures/CMakeLists.txt (+2/-1) tests/plugins/Ubuntu/Gestures/TestItem.cpp (+30/-0) tests/plugins/Ubuntu/Gestures/TestItem.h (+33/-0) tests/plugins/Ubuntu/Gestures/tst_FloatingFlickable.cpp (+122/-0) tests/plugins/Ubuntu/Gestures/tst_FloatingFlickable.qml (+80/-0) tests/plugins/Ubuntu/Gestures/tst_TouchGate.cpp (+1/-23) |
| To merge this branch: | bzr merge lp:~dandrader/unity8/floatingFlickable |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Michael Zanetti (community) | 2015-04-17 | Approve on 2015-04-27 | |
| PS Jenkins bot | continuous-integration | Needs Fixing on 2015-04-24 | |
| Unity Team | 2015-04-17 | Pending | |
|
Review via email:
|
|||
Commit Message
Introducing FloatingFlickable
Description of the Change
* Are there any related MPs required for this MP to build/function as expected? Please list.
https:/
* 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?
Not applicable
* If you changed the UI, has there been a design review?
Not applicable
| Michael Zanetti (mzanetti) wrote : | # |
289+ Q_PROPERTY(
Would it make sense to keep the upstream Flickable api? Just a thought. Not insisting on this if it makes the code internally more complicated.
===
279+ A Flickable that doesn't require the item being flicked to be its child.
Should be made more clear. Also the regular flickable doesn't require the items to be childs. The main point of this is, that the items can still have mouse interaction with this one, even though they are not direct childs of the Flickable. In other words, this one is transparent to input unless it really detected a flick.
===
507+ // We shouldn't need the three lines below, but a compiz/unity7
Is this still valid or just coped from some other gesture component? IIRC it's been ages ago we were suffering from that (1.5 years or so). Is this still about the same regression?
===
Otherwise looks good. Using it in the desktop-spread and it works great.
| Daniel d'Andrada (dandrader) wrote : | # |
> 289+ Q_PROPERTY(
> NOTIFY directionChanged)
>
> Would it make sense to keep the upstream Flickable api? Just a thought. Not
> insisting on this if it makes the code internally more complicated.
I considered that, but Flickable's direction enum has more options, like vertical_
So all options from Flickable's direction enum I would have to drop the use of a DDA and write the touch handling from scratch for the FloatingFlickable. Totally doable but I rather avoid all this work unless we are planning those use those modes.
- 1733. By Daniel d'Andrada on 2015-04-24
-
Merge trunk
[ CI Train Bot ]
* New rebuild forced.
[ Daniel d'Andrada ]
* Tapping home key shows unity8-dash home added:
plugins/Utils/ElapsedTi mer.h plugins/ Utils/HomeKeyWa tcher.cpp
plugins/Utils/HomeKeyWa tcher.h plugins/ Utils/Timer. cpp
plugins/Utils/Timer. h tests/plugins/ Utils/homekeywa tchertest. cpp
[ Michał Sawicz ]
* Tapping home key shows unity8-dash home added:
plugins/Utils/ElapsedTi mer.h plugins/ Utils/HomeKeyWa tcher.cpp
plugins/Utils/HomeKeyWa tcher.h plugins/ Utils/Timer. cpp
plugins/Utils/Timer. h tests/plugins/ Utils/homekeywa tchertest. cpp
[ Albert Astals Cid ]
* Compile with Qt 5.5 (LP: #1437238)
* Different way of top aligning labels when the other one in the row
is multiline (LP: #1442085)
* make pot_file
[ Andrea Cimitan ]
* Set sourceSize for DashBackground.qml Image
[ CI Train Bot ]
* New rebuild forced.
* Resync trunk. added: po/sk.po
[ Daniel d'Andrada ]
* Move handling of command line options to a separate class
* Refactor tst_PhysicalKeysMapper. qml
[ Leo Arias ]
* For autopilot tests, use the device simulation scenarios from the
toolkit.
[ Leonardo Arias Fonseca ]
* For autopilot tests, use the device simulation scenarios from the
toolkit.
[ Michael Zanetti ]
* Make sure dnd mode is ended properly when drag gesture is cancelled
(LP: #1444949)
[ Michał Sawicz ]
* Fix flake8 warnings (LP: #1444170)
* Move mock indicator service to unity8-fake-env, as it's a binary-
dependent package.
[ Nick Dedekind ]
* Use asynchronous dbus requests for property updates. (LP: #1436982) - 1734. By Daniel d'Andrada on 2015-04-24
-
Improve documentation
| Daniel d'Andrada (dandrader) wrote : | # |
> 279+ A Flickable that doesn't require the item being flicked to be its
> child.
>
> Should be made more clear. Also the regular flickable doesn't require the
> items to be childs. The main point of this is, that the items can still have
> mouse interaction with this one, even though they are not direct childs of the
> Flickable. In other words, this one is transparent to input unless it really
> detected a flick.
Fixed
>
> ===
> 507+ // We shouldn't need the three lines below, but a compiz/unity7
>
> Is this still valid or just coped from some other gesture component? IIRC it's
> been ages ago we were suffering from that (1.5 years or so). Is this still
> about the same regression?
>
I don't know, I just copied it from tst_Directional
- 1735. By Daniel d'Andrada on 2015-04-24
-
Removing unneeded workaround
| Daniel d'Andrada (dandrader) wrote : | # |
> >
> > ===
> > 507+ // We shouldn't need the three lines below, but a compiz/unity7
> >
> > Is this still valid or just coped from some other gesture component? IIRC
> it's
> > been ages ago we were suffering from that (1.5 years or so). Is this still
> > about the same regression?
> >
>
> I don't know, I just copied it from tst_Directional
> about the same regression.
Ok, removed it.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:1735
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://
| Daniel d'Andrada (dandrader) wrote : | # |
On 27/04/15 07:40, Michael Zanetti wrote:
> Review: Needs Fixing
>
> Bad tags in this branch.
Fixed.
| Michael Zanetti (mzanetti) wrote : | # |
* Did you perform an exploratory manual test run of the code change and any related functionality?
yes. using it in desktop-stage
* Did CI run pass? If not, please explain why.
unrelated AP test failures
* Did you make sure that the branch does not contain spurious tags?
y

FAILED: Continuous integration, rev:1732 jenkins. qa.ubuntu. com/job/ unity8- ci/5569/ jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- vivid-touch/ 2316 jenkins. qa.ubuntu. com/job/ unity-phablet- qmluitests- vivid/732 jenkins. qa.ubuntu. com/job/ unity8- vivid-amd64- ci/734 jenkins. qa.ubuntu. com/job/ unity8- vivid-i386- ci/734 jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- runner- vivid-mako/ 2032 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-armhf/ 2314 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- vivid-armhf/ 2314/artifact/ work/output/ *zip*/output. zip s-jenkins. ubuntu- ci:8080/ job/touch- flash-device/ 19757
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: s-jenkins. ubuntu- ci:8080/ job/unity8- ci/5569/ rebuild
http://