Yes it's a pain. I'm investigating a new mechanism that could make things a lot better.
Xav On Fri, Feb 18, 2011 at 1:50 PM, Nathan <[email protected]> wrote: > I have not had the same problems as either of you, but I have found > the library projects to be a major pain during debugging. > > I have to refresh the library, then refresh the dependent projects. > When debugging, I get a shadow copy of the source coming up, but it > still honors breakpoints from the library project even when I can't > see them. > > If there is an error in an xml resource, I often have do clean > operations on all three projects. > > If it doesn't all get in sync, not only do I not see the code fix I > just made, but I might have strange resource errors where the numbers > get mixed up and the wrong images show up for the drawable > resources. > > Nathan > > -- > 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 > -- Xavier Ducrohet Android SDK Tech Lead Google Inc. http://developer.android.com | http://tools.android.com Please do not send me questions directly. 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
