On Fri, Apr 15, 2011 at 11:53 AM, Eric <[email protected]> wrote: > Ok, I can supply some info, but I don't think it will help. The > problem is with the debugger, not my setup. That is why my post was > terse, prompting Google to get their act together.
And as soon as you demonstrate proof that Google's the source of the difficulty, I doubt you'll get any quibbles. However, casting blame without proof is not going to win you friends. > I am running the debugger shipped with > Jetbrains IDEA You will notice that "Jetbrains" is not "Google", except perhaps via some sort of encryption algorithm. > The only changing variable there is the debugger. Period. When you contacted your IDE vendor (Jetbrains) regarding your problem with their product, what did they tell you? When you tested your application in Eclipse -- to prove that the problem is in Google's code and not Jetbrains' -- what did you find? -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Warescription: Three Android Books, Plus Updates, One Low Price! -- 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
