On Jan 19, 10:58 pm, Romain Guy <[email protected]> wrote:
> Everything is explained in the article I linked to. It is a much
> better design choice for the user and it is what matters. I know that
> developers are confused by this but I have yet to see a report of user
> complaints about this :)
>
> As for keeping a selection, again, read the article. It explains that
> you can use ListView's choice mode feature to keep a persistent
> selection.
Thanks for answering. But I respectfully disagree some for the design
decision you asserted there. I am be wrong, but I am sure I am not
alone for what I think of.
I read your recommendation about "Focusable in touch mode is a
property that you can set yourself either from code or XML. However,
it should be used sparingly and only in very specific situations as it
breaks consistency with Android normal behavior." -- let's say we have
spinner view, I think it's entirely natural to make it focusable/
selectable in touch mode.
In a broader concept, the above assertion may not be true either.
Let's look at the 'dialer' application: when I touch a missed call
item in the call log, I basically return the call. But I think my
natural intent may be looking for more details for that missed call
instead of calling back.
>
>
>
> On Mon, Jan 19, 2009 at 10:55 PM, Developer <[email protected]> wrote:
>
> > On Jan 19, 10:07 pm, Romain Guy <[email protected]> wrote:
> >> You can't.
> >> Seehttp://android-developers.blogspot.com/2008/12/touch-mode.html
> >> for more information and what to use instead.
>
> > This seems to be a natural feature request for some scenarios. I
> > wonder why the android framework does not provide such a mechanism. a
> > weird design choice....
>
> >> On Mon, Jan 19, 2009 at 9:27 PM, Developer <[email protected]>
> >> wrote:
>
> >> > I have list of items displayed in ListActivity by
>
> >> > onCreate() {
> >> > ...
> >> > setListAdapter(new SimpleAdapter(this, myData,
> >> > android.R.layout.simple_list_item_1,
> >> > new String[] {MyItemClass.Items },
> >> > new int[] { android.R.id.text1 }));
> >> > }
>
> >> > when I mov my key up and down, the item get highlighted, which is
> >> > great. But when I push the menu button by
>
> >> > public boolean onCreateOptionsMenu(Menu menu) {
> >> > super.onCreateOptionsMenu(menu);
> >> > menu.add(0, ADD_ID, 0, R.string.menu_ADD_NEW_ITEM);
> >> > menu.add(0, DELETE_ID, 0,
> >> > R.string.menu_DELETE_SELECTED_ITEM);
> >> > return true;
> >> > }
>
> >> > the highlight goes away. Can I somehow keep the highlight even after
> >> > the menu button is clicked?
>
> >> > Thanks a lot,
>
> >> --
> >> 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
>
> --
> 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
-~----------~----~----~----~------~----~------~--~---
