On Wed, Jun 13, 2012 at 12:47:50PM -0700, kadmos wrote: > I dont expect my problems to be solved for me - I've been working on the > Android platform for two years now - alone. This is the first time I have > been this stuck.
I believe the point was, if you don't post the relevant portion of your code, how does ANYONE know that it's not YOUR code that's wrong? Nobody here (that I know of) is a mind reader. You're saying that Google's code is wrong, while it's working everywhere else except your app, and you won't post the relevant code from your app. How is anyone to asume anything other than that the flaw is in your app? Think about it.... Then post the relevant portion of your code, and maybe, if you haven't already been added to everyone's "send straight to /dev/null" list, you might actually get some help fixing your app. Later, --jim -- THE SCORE: ME: 2 CANCER: 0 73 DE N5IAL (/4) | "This 'telephone' has too many spooky1...@gmail.com | shortcomings to be seriously considered < Running Mac OS X Lion > | as a means of communication. The device ICBM / Hurricane: | is inherently of no value to us." 30.44406N 86.59909W | (Western Union internal memo, 1876) Android Apps Listing at http://www.jstrack.org/barcodes.html -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
