On Tue, Apr 24, 2012 at 07:02:52AM -0400, Mark Murphy wrote:
> which is why we keep asking developers to post stack traces rather than
> just exception names
Which would have been a lot easier to do, if I had it. Like I said, I'd
tried it earlier, and when it didn't work, just deleted it (planning to
come back to it later---I was VERY tired all day yesterday). It wasn't
until later that I really started thinking that I HAD done it right, and
started looking into it a lot more, and finally, posted here to find out
if I was at least doing it the right way.
I just re-created the code to try and duplicate the problem, and it works
perfectly now. All I can say is that in my exhausted state yesterday, I
screwed something up and didn't see it (permanent cancer #1 aftermath
blah blah blah). Yeah, that happens, and is annoying as hell, especially
when I don't catch it, and end up making a fool of myself here.
Later,
--jim
--
THE SCORE: ME: 2 CANCER: 0
73 DE N5IAL (/4) MiSTie #49997 < Running FreeBSD 7.0 >
spooky1...@gmail.com ICBM/Hurricane: 30.44406N 86.59909W
"'Wrong' is one of those concepts that depends on witnesses."
--Catbert: Evil Director of Human Resources (Dilbert, 05Nov09)
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
