Didn't eat my wheaties this morning. I can simply pass in the reference during the construction of the handler.
Mark, thanks for the feedback. I agree that broadcasting through an excepted context is a little dicey, but it seems to work for now. I can't think of a better alternative context-less thread -> android communication short of something horribly inefficient like file polling, but I'm open to suggestions. I am building a "whatever" app to report exceptions, so using Flurry or DroidDrop would defeat the purpose. You are right in that, tragically, "whatever" cannot self- reference its own automated exception reporting capabilities. ;) thanks for the input, -Jess On Feb 15, 2:01 pm, Mark Murphy <[email protected]> wrote: > laphroaig15 wrote: > > Is there some way to interact with the android packages to > > retrieve a context in a static manner? > > Not really. The Application object is a singleton, as is any Service you > have running, but I am not aware of ways to obtain those from a static > method. > > Moreover, please do not try binding to a service from an exception > handler. Broadcasting an Intent may be safe, but I'm not completely > confident of that, either. > > Even simpler is just to use Flurry or DroidDrop or whatever to report > your exceptions. > > Trying to have an Android component respond to an exception may prove > troublesome, particularly if the exception is thrown from the Android > component in question. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://twitter.com/commonsguy > > Android Development Wiki:http://wiki.andmob.org -- 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
