Yes, the ID is used to propagate the saved state to the appropriate view in the next instance. Use different IDs. Why do you even want to use the same ID?
On Tue, Mar 17, 2009 at 12:45 PM, skink <psk...@gmail.com> wrote: > > > > On 17 Mar, 18:36, Romain Guy <romain...@google.com> wrote: > > Oh yeah, we fixed that in Cupcake. > > > > But the bottom line is: don't use the same id for Views of different > types. > > ok, thanks for info > > but if i used the same ids for the same View types (for example two > ListViews) how its supposed to work? we will not have > ClassCastException but i think different SavedStates would be used by > different ListViews... > > > -- Dianne Hackborn Android framework engineer hack...@android.com 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 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 -~----------~----~----~----~------~----~------~--~---
