In Ubuntu-clock-app, if you delete the last world city the count property remains set at one instead of zero. If you add 2 world cities (count=2), and then delete one, the count changes to 1. If you delete the last one, the count remains as 1.
To reproduce the bug:
- launch the app with autopilot:
autopilot3 launch -i Qt qmlscene ../../app/ubuntu-clock-app.qml -I ../../builddir/backend/
- add a World city, clicking on the "Add City" button and selecting a city
- with autopilot3 vis verity the count property of QQuickRepater with objectName "userWorldCityRepeater" it will be set at 1, close autopilot vis
- swipe and delete the previously added city
- launch autopilot3 vis again and verity the count property of QQuickRepater with objectName "userWorldCityRepeater" it will still be set at 1 instead of decreasing of one and be set to 0.
In Ubuntu-clock-app, if you delete the last world city the count property remains set at one instead of zero. If you add 2 world cities (count=2), and then delete one, the count changes to 1. If you delete the last one, the count remains as 1.
To reproduce the bug: ubuntu- clock-app. qml -I ../../builddir/ backend/
- launch the app with autopilot:
autopilot3 launch -i Qt qmlscene ../../app/
- add a World city, clicking on the "Add City" button and selecting a city epeater" it will be set at 1, close autopilot vis epeater" it will still be set at 1 instead of decreasing of one and be set to 0.
- with autopilot3 vis verity the count property of QQuickRepater with objectName "userWorldCityR
- swipe and delete the previously added city
- launch autopilot3 vis again and verity the count property of QQuickRepater with objectName "userWorldCityR