On Jul 9, 4:28 pm, eags <eagsala...@gmail.com> wrote: > I did what you said and it worked. This is actually exactly what the > Alarm Clock application does since when you click on an alarm it > doesn't select the entireListViewelementbut just the clock and > message. However I still have a couple problems with this: > > 1. Why??? I find this behavior to be very confusing especially when > other simpler list view item layouts work just fine at the top level > (for example browser options clicking selects the entireelement > including the checkbox which is what I want) > 2. This actually really screws up my code because now my > OnItemClickListener which was returning to me the index which is > useful now just has a reference to theelement. I could probably > figure out the index either way but it seems like a pointless mess. > > Is there some piece of documentation you could point me to that > explains what is going on here? It seems very quirky to me.
I had the exact same issue and filed an enhancement request with fix for the underlying problem in the UI toolkit. Please take a look at this request and 'star' it if you support this change: http://code.google.com/p/android/issues/detail?id=3414 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
