count property of Qquickrepeater is not decreased to zero after deleting the last element

[Carla Sella]

In Ubuntu-clock-app, if you delete the last world city the count property of Qquickrepeater 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 verify 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 verify 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.

[Carla Sella (carla-sella)]

If you look at the attached screenshot that I took of autopilot vis after deleting a world city I had added, you can see that in the clock
app the world city is gone, deleted, but in autopilot vis the world city is still there, it has not been delete, hence the count set at 1, at
least I think so!

[Tim Peeters (tpeeters)]

This sounds like an upstream bug in Repeater to me.

Can you create a small&simple test program to reproduce the issue?

[Zsombor Egri (zsombi)]

GC (Garbage Collector) is the one responsible to delete this. And unfortunately we cannot really do much about this.

However, I would implement the feature using a ListView, where the model is a list of cities. ListView at least handles this much better. and after all, this is not a toolkit bug.

[Nekhelesh Ramananthan (nik90)]

Actually just a few days back, I replaced the repeater with a listview and I was still hitting this issue. But I will try to create a simple app to reproduce this issue.

[Ubuntu Phone Apps Jenkins Bot (ubuntu-phone-apps-jenkins-bot)]

Fix committed into lp:ubuntu-clock-app at revision 366, scheduled for release in ubuntu-clock-app, milestone 3.5