Android 为View分配id



Android id overview
An Android id is an integer commonly used to identify views; this id can be assigned via XML (when possible) and via code (programmatically.) The id is most useful for getting references for XML-defined Views generated by an Inflater (such as by using setContentView.)

Assign id via XML
Add an attribute of android:id="@+id/somename" to your view.
When your application is built, the android:id will be assigned a unique int for use in code.
Reference your android:id’s int value in code using "" (effectively a constant.)
this int can change from build to build so never copy an id from gen/, just use "".
(Also, an id assigned to a Preference in XML is not used when the Preference generates its View.)
Assign id via code (programmatically)
Manually set ids using someView.setId(int);
The int must be positive, but is otherwise arbitrary- it can be whatever you want (keep reading if this is frightful.)
For example, if creating and numbering several views representing items, you could use their item number.
Uniqueness of ids
XML-assigned ids will be unique.
Code-assigned ids do not have to be unique
Code-assigned ids can (theoretically) conflict with XML-assigned ids.
These conflicting ids won’t matter if queried correctly (keep reading).
When (and why) conflicting ids don’t matter
findViewById(int) will iterate depth-first recursively through the view hierarchy from the View you specify and return the first View it finds with a matching id.
As long as there are no code-assigned ids assigned before an XML-defined id in the hierarchy, findViewById( will always return the XML-defined View so id’d.
Dynamically Creating Views and Assigning IDs
In layout XML, define an empty ViewGroup with id.
Such as a LinearLayout with android:id="@+id/placeholder".
Use code to populate the placeholder ViewGroup with Views.
If you need or want, assign any ids that are convenient to each view.
Query these child views using placeholder.findViewById(convenientInt);

API 17 introduced View.generateViewId() which allows you to generate a unique ID.

If you choose to keep references to your views around, be sure to instantiate them with getApplicationContext() and be sure to set each reference to null in onDestroy. Apparently leaking the Activity (hanging onto it after is is destroyed) is wasteful.. 🙂

Reserve an XML android:id for use in code
API 17 introduced View.generateViewId() which generates a unique ID. (Thanks to take-chances-make-changes for pointing this out.)*

If your ViewGroup cannot be defined via XML (or you don’t want it to be) you can reserve the id via XML to ensure it remains unique:

Here, values/ids.xml defines a custom id:

<?xml version="1.0" encoding="utf-8"?>

Then once the ViewGroup or View has been created, you can attach the custom id

Conflicting id example
For clarity by way of obfuscating example, lets examine what happens when there is an id conflict behind the scenes.


<?xml version="1.0" encoding="utf-8"?>
android:orientation="vertical" >
android:orientation="horizontal" >

To simulate a conflict, lets say our latest build assigned an int value of 12..

Next, defines some adds views programmatically (via code):

int placeholderId =; // placeholderId==12
// returns placeholder which has id==12:
ViewGroup placeholder = (ViewGroup)this.findViewById(placeholderId);
for (int i=0; i<20; i++){
TextView tv = new TextView(this.getApplicationContext());
// One new TextView will also be assigned an id==12:
So placeholder and one of our new TextViews both have an id of 12! But this isn’t really a problem if we query placeholder’s child views:

// Will return a generated TextView:

// Whereas this will return the ViewGroup placeholder;
// as long as its remains 12:
*Not so bad