Hi oregonduckman, For the "R cannot be resolved" issue, make sure your R import is in the form:
import your.package.name.R Sometimes a default of: import android.R will appear (I've not figured out the metric that causes this to occur). Remove the android.R import, and replace it with your.package.name.R. Hopefully this will help. As far as the build path errors issue, again I've not figured out exactly what triggers this, but if you touch any of your project files (i.e., make an inconsequential change and resave it, so Eclipse thinks it needs to be rebuilt, or use a Touch utility), and rebuild, this should hopefully help too. You may have to do it twice. I usually just pick one of the project's .java files and touch that. Hope this helps! XCaf On Dec 28, 3:41 pm, oregonduckman <oregonduck...@gmail.com> wrote: > I frequently receive the error "r cannot be resolved" when adding > functionality to an application and I have no idea why this happens. > The change can be as simple as adding an ArrayList when the error > appears in Eclipse. > > I have also seen the same kind of thing with the error message "The > project cannot be built until build path errors are resolved" > appearing after closing Eclipse then re-opening it with a given > project. > > Are these just Eclipse/Android Plugin idiosyncrasies or I am doing > something wrong? > > My development environment is Leopard+ Eclipse Platform > 3.5.1.M20090917-0800+ Android Development Tools > 0.9.5.v200911191123-20404 -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to android-beginners+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
