To be pretty honest, if you're throwing dialogs up from systems code,
you might be having a design issue to begin with. No user wants to
see tons of dialogs saying "download failed," or "could not connect to
service," etc... I think this is a key point that a lot of people
miss in architecting th
That's the thing. You don't show any dialogs outside of an activity.
This is not good practice, log the trace.
If you want to be messy, you can have a singleton to which activities
register to.
Then call functions in that singleton.
On Mon, Sep 19, 2011 at 3:33 AM, JoachimG wrote:
> Hi ppl!
>
>
On Mon, Sep 19, 2011 at 5:33 AM, JoachimG wrote:
> Is there a way to show a error dialog deep within the system of my app?
>
None that I'd recommend. If something is going wrong "deep within the
system" of your app, should your user really need to be informed?
What is your use case?
---
Hi ppl!
Is there a way to show a error dialog deep within the system of my
app?
Because only an activity is able to call showdialog i have to throw
all excetions out until i can use a try catch with showdialog in an
activity. Is there a way to call showdialog deeper in the system of an
applicatio
4 matches
Mail list logo
