Ah... we've all been there. Any programmer/developer can relate to the situation that one missing silly semicolon messing up your code can be overlooked for a looooooooooooong time, followed by a big forehead-slapping.
Anywhose, it's quite amazing what info you can get by just examining your threads' stack-traces, isn't it? It's my first go-to method when i'm faced with an ANR or similar situation. -- 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
