Merge lp://qastaging/~uriboni/camera-app/reset-zoom-ui into lp://qastaging/camera-app/staging

Proposed by Florian Boucault
Status: Merged
Approved by: Florian Boucault
Approved revision: 603
Merged at revision: 609
Proposed branch: lp://qastaging/~uriboni/camera-app/reset-zoom-ui
Merge into: lp://qastaging/camera-app/staging
Diff against target: 204 lines (+80/-28)
4 files modified
ViewFinderOverlay.qml (+7/-0)
tests/autopilot/camera_app/emulators/main_window.py (+20/-1)
tests/autopilot/camera_app/tests/test_capture.py (+6/-27)
tests/autopilot/camera_app/tests/test_zoom.py (+47/-0)
To merge this branch: bzr merge lp://qastaging/~uriboni/camera-app/reset-zoom-ui
Reviewer Review Type Date Requested Status
Florian Boucault Pending
PS Jenkins bot continuous-integration Pending
Review via email: mp+278612@code.qastaging.launchpad.net

This proposal supersedes a proposal from 2015-11-18.

Commit message

Correctly reset the zoom UI when the actual zoom level of the camera resets due to switching cameras or recording modes

Description of the change

Correctly reset the zoom UI when the actual zoom level of the camera resets due to switching cameras or recording modes

To post a comment you must log in.
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote : Posted in a previous version of this proposal
review: Needs Fixing (continuous-integration)
Revision history for this message
Florian Boucault (fboucault) wrote : Posted in a previous version of this proposal

We have a binding one way.

         Binding { target: camera; property: "currentZoom"; value: zoomControl.value }

We ideally would want one the other way no? This could probably be achieved without binding loop issues with something like:

Connections {
   target: camera
   onCurrentZoomChanged: zoomControl.value = camera.currentZoom
}

review: Needs Information
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote : Posted in a previous version of this proposal
review: Needs Fixing (continuous-integration)
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote : Posted in a previous version of this proposal
review: Needs Fixing (continuous-integration)
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote : Posted in a previous version of this proposal
review: Needs Fixing (continuous-integration)
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote : Posted in a previous version of this proposal
review: Needs Fixing (continuous-integration)
Revision history for this message
Ugo Riboni (uriboni) wrote : Posted in a previous version of this proposal

> We have a binding one way.
>
> Binding { target: camera; property: "currentZoom"; value:
> zoomControl.value }
>
> We ideally would want one the other way no? This could probably be achieved
> without binding loop issues with something like:
>
> Connections {
> target: camera
> onCurrentZoomChanged: zoomControl.value = camera.currentZoom
> }

This actually causes lots of binding loop warnings when zooming, as the value changes:

ViewFinderOverlay.qml:743:13: QML Binding: Binding loop detected for property "value"

I don't think they are a problem, but it still not nice to have them. Should I revert to my previous implementation ?

Revision history for this message
PS Jenkins bot (ps-jenkins) wrote : Posted in a previous version of this proposal
review: Needs Fixing (continuous-integration)

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
The diff is not available at this time. You can reload the page or download it.

Subscribers

People subscribed via source and target branches