Shared user IDs have nothing to do with resource IDs. A resource ID (for applications) is meaningless without an association with the .apk/package it is in, but a shared user ID is unrelated to that.
On Tue, Jul 20, 2010 at 9:42 AM, Android <[email protected]> wrote: > Hi, > > If I am not wrong with the way android:sharedUserId is intended to > work, then my question is how to avoid overlapping resource IDs? appt > seems to aways start IDs at the same initial value (i.e. drawables at > 0x7f020000), so there will be sort of conflict or ambiguation. As for > now I failed to get that cleared w/o digging in OS sources. Or I miss > anything, like magic "undocumented" appt option (not that aapt is > documented at all)? > > -- > 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]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- 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, and so won't reply to such e-mails. 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
