That's correct, the @*android notation is used to access private
resources which you should *never* do unless you build the platform at
the same time as your app. Private resources use unstable generated
ids which can and will change in each version of the platform. If you
were to use private resources in your app you would most likely see
your app break with the next version of Android.

On Thu, Dec 3, 2009 at 9:43 PM, James Wang <jameswangc...@gmail.com> wrote:
> Dianne mentioned we can use "@*android:type/name" to reference
> resource added to framework-res.apk at "what's the best way for OEM to
> organize it's own resources?"(http://groups.google.com/group/android-
> framework/browse_thread/thread/e9974bd5a42af10a/1f7055086f5489a7).
>
> And I did see it is used in android source and looks like it is used
> to refer to internal resource not public, am I right?
>
> I wonder whether it is possible to refer to internal resource without
> errors in Eclipse. I tried but adt reports error.
>
> Best regards.
>
> James
>
> --
> 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
>



-- 
Romain Guy
Android framework engineer
romain...@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

Reply via email to