On Wed, Feb 15, 2012 at 5:49 PM, Weston Weems wrote:
> it doesnt even seem there is a decent way to
> test to see if context is
> 1) a valid ui context from which I can pop dialogs, show dialog fragments
> etc
>
Don't use a base Context, use an Activity, which itself is a Context, but
one assoc
Ok,
I've encountered several cases where I'd like to instantiate classes
that exist as a child of my application subclass, events fire say like
a communications error, and we'd like to be able to popup a sort of
general communication error anywhere in my app.
Another example is say where applicab
2 matches
Mail list logo
