That discussion was about using the same ID in different layouts that are NOT mixed together in the same view hierarchy, in which case yes it is perfectly okay.
The only restriction here is that the default implementation of the system for saving your state is to use the view IDs to remember individual view states and restore it later for that view hierarchy. From that follows the only restrictions on IDs, if you want to keep the mechanism in place. 2009/3/17 skink <[email protected]> > > > > Dianne Hackborn napisał(a): > > 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? > > > > > also i had similar problem some time ago > > http://groups.google.com/group/android-developers/browse_thread/thread/a27bf316d1ed7027/30b8f6d1c9d85365?q= > and was told its ok to have same ids. > > > > > -- Dianne Hackborn 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 -~----------~----~----~----~------~----~------~--~---
