Ok, thanks, this was exactly what I needed to know. The case where the
system kills the app while being in the background and not in first screen.
Am Montag, 25. Februar 2013 18:21:27 UTC+1 schrieb Streets Of Boston:
>
> In addition to Treking's answer;
>
> Never rely on the order in which (you
In addition to Treking's answer;
Never rely on the order in which (you think that) activities are started to
initialize or modify static/global data.
E.g.
User goes through your app, starting from the homescreen, going from
Activity A then to Activity B then to C. This could be order in which
Ok, thanks. I couldn't reproduce this case, so I wasn't sure. I'll handle
it in other way then.
Am Montag, 25. Februar 2013 17:34:43 UTC+1 schrieb TreKing:
>
>
> On Mon, Feb 25, 2013 at 3:52 AM, user123
> > wrote:
>
>> And I'm wondering, if there's any case where I can get a null pointer?
>> B
On Mon, Feb 25, 2013 at 3:52 AM, user123 wrote:
> And I'm wondering, if there's any case where I can get a null pointer?
> Because e.g. the system kills the app while it's in the background, and
> tries to restart it in the last screen - since the variable is only
> initialized in the launcher sc
I have an instance variable in a singleton class which I'm using in all the
app. It's basically a global configuration parameter.
I initialize it in the first (launcher) screen of the app. The app will not
continue without this initialization (where it's sure that the variable is
not null). And
5 matches
Mail list logo
