Merge lp://staging/~charlesk/indicator-transfer/per-transfer-actions into lp://staging/indicator-transfer/14.10
Status: | Merged |
---|---|
Approved by: | Ted Gould |
Approved revision: | 12 |
Merged at revision: | 7 |
Proposed branch: | lp://staging/~charlesk/indicator-transfer/per-transfer-actions |
Merge into: | lp://staging/indicator-transfer/14.10 |
Diff against target: |
693 lines (+285/-149) 8 files modified
MERGE-REVIEW (+40/-31) README (+11/-10) include/transfer/transfer.h (+9/-6) src/CMakeLists.txt (+1/-0) src/transfer.cpp (+72/-0) src/view-gmenu.cpp (+102/-81) src/world-dbus.cpp (+45/-17) tests/test-view-gmenu.cpp (+5/-4) |
To merge this branch: | bzr merge lp://staging/~charlesk/indicator-transfer/per-transfer-actions |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Ted Gould (community) | Approve | ||
Review via email: mp+224537@code.staging.launchpad.net |
Commit message
Create per-transfer actions for simpler state lookup by renderers. Previously this was done as a single action that contained a map of unique transfer ids to states.
Description of the change
== Description of the Change
1. Instead of having a single GAction "transfer-states" that gives *all* transfers' states inside a map, Have individual per-transfer actions so that it's easier to look up a transfer's state in the renderer.
2. Ensure that the Transfer's opaque unique id exposed in our GActions/GMenus really is opaque. Previously it leaked the object path of the corresponding com.canonical.
== MP Submission Checklist
> * Are there any related MPs required for this MP to build/function as expected? Please list.
Yes, three:
1. https:/
2. https:/
3. https:/
> * Is your branch in sync with latest trunk? (e.g. bzr pull lp:trunk -> no changes)
Yes
> * Did the code build without warnings?
Yes
> * Did the tests run successfully?
Yes
> * Did you perform an exploratory manual test run of your code change and any related functionality?
NO: suru icons MP could not be built into a deb, so I was not able to properly test the indicator's header icon changes at <http://
YES: Other than the above exception, the exploratory manual test run was successful.
> * Has your component test plan been executed successfully on emulator or a physical device?
Yes, N4 mako
> * Please list which manual tests are germane for the reviewer in this MP.
indicator-
Couldn't find anything I wanted to complain about :-(