← Back to team overview

touch-packages team mailing list archive

[Bug 1421653] Re: Changing ItemSelector model sets currentIndex to 0

 

Modxel change resets the index, like any model change in a mode-based
component (see PathView, ListView, etc). No way to stay in the original
index as what if that is out of the model count?

** Changed in: ubuntu-ui-toolkit (Ubuntu)
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1421653

Title:
  Changing ItemSelector model sets currentIndex to 0

Status in ubuntu-ui-toolkit package in Ubuntu:
  Won't Fix

Bug description:
  Repro:
  1. Have expanded ItemSelector
  2. Set currentIndex to something other than 0 by tapping the second or third item in an ItemSelector

  What happens:
  currentIndex is sat to 0, i.e. the selected item is changed

  What should have happened:
  currentIndex should have remained

  Example: http://pastebin.ubuntu.com/10205382/

  Might be invalid/unfixable, and that's ok, but it might deserve a note
  in the docs?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1421653/+subscriptions


References