Transition to the new header APi
Bug #1360869 reported by
Nekhelesh Ramananthan
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Quick Memo |
Fix Released
|
High
|
Stefano Verzegnassi |
Bug Description
On looking through the code, I noticed that you used Tools: ToolbarItems{}. The SDK have introduced a new headers API where the define the header actions, backAction, states etc inside head{}. Check out the PageHeadConfigu
Related branches
lp:~verzegnassi-stefano/quick-memo/fix-1360869-1366076
- Stefano Verzegnassi: Approve
-
Diff: 525 lines (+179/-204)4 files modifiedcomponents/AddMemo.qml (+1/-4)
components/MainPage.qml (+118/-119)
components/MemoPage.qml (+17/-30)
components/MultiSelectionHandler.qml (+43/-51)
Changed in quick-memo: | |
importance: | Medium → High |
milestone: | none → 0.3 |
Changed in quick-memo: | |
status: | Triaged → In Progress |
assignee: | nobody → Stefano Verzegnassi (verzegnassi-stefano) |
Changed in quick-memo: | |
status: | In Progress → Fix Committed |
Changed in quick-memo: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I think to switch to new header API for the release 0.3, since I still have to see how to rewrite MultiSelectionH andler. qml (PageHeadConfig uration property in Ubuntu. Components. Page is read-only).
This is for certain a priority for the next release.