On Wed, Sep 19, 2012 at 6:54 AM, Heila van der Merwe wrote:
> So just to clarify: the advantage of using a Singleton object will be that
> if the app is killed, the Singleton object can just be recreated when it is
> needed. So you could use a Singleton object in the Application class to
> assure
So just to clarify: the advantage of using a Singleton object will be that
if the app is killed, the Singleton object can just be recreated when it is
needed. So you could use a Singleton object in the Application class to
assure that it will be initialised when it is needed and the Singleton
o
m not 100% sure but i feel this could help
http://developer.android.com/reference/android/app/Activity.html#onSaveInstanceState(android.os.Bundle)
but i feel if u can save the state of the objects
onSaveInstanceState(android.os.Bundle)
and restore them on onRestoreInstanceState(android.os.Bundle
On Thu, Sep 23, 2010 at 8:36 PM, elubin wrote:
> That absolutely sounds like what is happening, but WHY would my app be
> killed and restarted?
>
I'm guessing because it's idle long enough and Android feels like killing
it. If you're leaving your app alone over night, likely your phone is going
I think the lesson is that an Android application and
android.app.Application are frequently mistakenly assumed to behave the same
as an "application" on other operating systems.
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to th
That absolutely sounds like what is happening, but WHY would my app be
killed and restarted? You are correct, if it gets restarted on the
main window then i am not refilling my application data. I only fill
it on the login window. Do I misunderstand how application data is
supposed to work?
I h
6 matches
Mail list logo
