Scope of R.id values

Question

I\'m looking for ways to reduce what I would call \"id pollution\" in my apps. From what I can tell, R.id is global to the application, so in every Activity I

Answer 1

You're fine to use the same id across multiple elements, as long as they aren't in the same view. So, all your save buttons could have the id of btn_save and as long as there aren't two of them in the same layout file, or attached layouts, then you're fine.

Answer 2

I use:

R.id.activityName_type_action

where type may be [btn|txtview|edittext|listview...]

and action is something like [save|del|accept|name|pin...]

It's pretty verbose, but this way I can guess the identifier name from the activity without having to continuosly check the xml layout.

For example:

R.id.loginpin_btn_accept

R.id.loginpin_txtview_pin

Answer 3

The other answers will work, but you could also make a save_button.xml in your layout folder, with <Button> as the root tag. Then reference that guy's id in those places that you need it. This means you only need to define one "save" button, and use it everywhere.