Hi Romain, In my mind there are (at least) two ways to use a ListView:
One is when you want to let the user pick a single item then immediately move to some other Activity (this works perfectly as described). For example, you present the user with a list of cities, as soon as they click "New York", we move them to a new Activity. So there's no issue about letting the item remain focused. The other is the problem I'm facing, where I don't want to immediately perform some action when the user clicks a ListView item. Maybe the user can click the item (or multiple items), then perform some delayed action. Something like: "Pick 4 cities you want to visit, then hit OK." <ListView here> <OK button here> here the user would tap multiple ListView items, each of which should remain "selected". In this case, what would you recommend we do? Should each ListView item be a composite ChechBox + TextView control for example? So instead of relying on the ListView to indicate "selected-ness", I simply put a checkmark next to the items that the user has tapped thus far? Thanks On Jun 19, 1:15 pm, Romain Guy <[email protected]> wrote: > > I read through the document linked, but still cannot appreciate the > > rationale behind disallowing a ListView item from having a 'selected' > > color when in TouchMode, > > With your solution, there is no distinction between a "checked" item and the > selection (the selection is the highlight that moves when the user moves > around with the trackball/dpad/keyboard/etc.), which is confusing. > > The selection disappears in touch mode because it is in our opinion the best > way to handle the dual navigation mode (touch and non-touch.) If we kept the > selection, what should happen when the user scrolled the list with the touch > screen and then tried to use the trackball/dpad again? The list could > immediately scroll back to where the selection is (very jarring effect) or > the selection could reappear on the current screen (which is equivalent to > having lost the selection in the first place.) > > You can do whatever you want of course but you are going against Android's > UI guidelines and your application behaves differently from all other apps. > Which is bad for your users. I **strongly** recommend that you follow what I > explained in the article linked in one of the previous messages in this > thread. > > -- > Romain Guy > Android framework engineer > [email protected] > > Note: please don't send private questions to me, as I don't have time to > provide private support. All such questions should be posted on public > forums, where I and others can see and answer them --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
