Do not rename Android resources in the Eclipse IDE
Eclipse IDE should be really good. It has loads of functionality and has been around long enough but it is still SOOO flaky. For instance, I ended up with two text fields in two different layouts that were called the same thing. This should be fine since the "view" is found in each activity and will only find the one in the current layout. However, you try changing the name of ONE of them in the Eclipse properties window and all hell breaks loose. Whether you select to "update references" or not, it will change all instances of the name in both layout files and both activity classes - not what you want.
I also noticed that if you type something into the properties box and press enter, when the update references dialog comes up, if you then change what you typed in to something else, it still uses the original text.
The best way to change them is to edit the layout XML directly and change the relevant ID. The resources will pick up the change and there will be no updating of references.
Other problems in Eclipse:
I also noticed that if you type something into the properties box and press enter, when the update references dialog comes up, if you then change what you typed in to something else, it still uses the original text.
The best way to change them is to edit the layout XML directly and change the relevant ID. The resources will pick up the change and there will be no updating of references.
Other problems in Eclipse:
- Sometimes you cannot start debugging. I think if you kill the debugger too soon after starting it, it gets stuck and you have to restart the IDE.
- Updating things directly in the properties menu is basically a bad idea and causes all kinds of weird stuff to happen with focus.
- If you edit the strings resource XML (and possibly other files) and then change to the graphical layout and paste into the edit box, it actually pastes the code into the XML you were just editing which then might or might not create an error depending on what you pasted where!
- Callstacks during debugging are basically almost impossible to work out. Also, if exceptions occur when debugging, the debugger rarely takes you to the point where the exception occurs, but to some other weird place (that might be Android specific though)
- Attaching source code is a nightmare - I've basically given up.