13 февраля 2012 г. 12:25 пользователь JJ B <[email protected]>написал:
> My code runs fine for a few days with no changes and then...boom! > doesn't play nice anymore by forcing me to import android.R for no > reason whatsoever. I've increased the memory allocation as > recommended, carefully "cleaned" upon any changes, and prayed to the > Android Gods for Eclipse to run as smoothly as possible. > That's possible if you've been editing resources - Android tools occasionally fail to regenerate correct resource identifiers, which can cause your app to crash with mysterious "illegal typecast" exceptions, findViewById randomly returning null, etc. I suppose the imports can get messed up if you do "organize imports" after having cleaned the project, in the middle of a rebuild. You also might want to take a look at your Eclipse preferences, under Java / Editor / Save Actions, perhaps disabling "organize imports" there. > > I'm sure there's an archived thread somewhere out there saying I > should be coding standing on one foot, facing due West and with all > planets aligned...in case there is, can someone point me to that > information? :) > Actually, it's human sacrifice :) > > Thanks! > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
