Picker: selectedIndex changes incorrectly when removing model entries

I've now switched to using PageHeadSections for this, and am experiencing much the same issue. If I insert something before the current index I need to add 1 to the selected index to compensate, and the reverse for removal.

Your sample code doesn't remove items from the model, but inserts.

The behaviour you experience is due to both components using ListView (PathView or GridView behaves the same). When you alter the model, the currentIndex won't necessarily point to the same item was pointing anymore. Removing an element from the ListView will cause currentIndex to change as well. This bug is more related to ListView than to Picker itself.

Try the same with a ListView, and I'm sure you'll experience the same.

OK, the section headers are not the same issue as the picker component. I've attached a new example showing both.

With both components set to index 12:
  After removing item 8, the section header moves to item 13, but the picker jumps to item 7.
  After removing item 3, the section header moves to item 13, whereas the picker remains on item 12.

I can't test this with a ListView directly, as it does not have a selectedIndex.
So, the picker jumps down to the deleted item on some indices and remains pointing at the correct item on others.
I've registered a separate bug for the off by one behaviour of the section header (bug #1493040).

ListView has currentIndex, which is the selected one. Picker.selectedIndex works with that property as well. Then Sections.selectedIndex is not interacting with any ListView or such, so that works a bit differently, it always moves to the last item in the model when changes afaik.

Tried it with ListView by printing numModel.get(listview.currentIndex).num.
This behaves correctly, and always stays on the 12, until that item is removed.

The issue described is present in ONLY the Picker component.