If the process is being killed, the Application is gone too.
On Tue, Feb 1, 2011 at 9:38 PM, bruce palant...@gmail.com wrote:
If your process is killed, all the activities are killed so its not
like the globals are released and you still have activities running
causing a force close. Sounds
Wished Android made a class that it does not touch until the app is
totally dead...so when you tap back on the app, it will start back
from the beginning.
Oh well. I will just redesign to be better then.
Thanks group.
On Feb 2, 4:09 am, Mark Murphy mmur...@commonsware.com wrote:
If the process
Something else is causing your Force Close. Read the exception
report in LogCat and dig into the actual cause.
Read up on the Activity lifecycle, in particular the bubble
that reads Other applications need memory:
http://developer.android.com/reference/android/app/Activity.html
The Android OS
Thanks for your replyI was looking at that article before.
Now...my app has lots of activities. The first activity loads up global
values and so on and shows the intro screen. Now, I am thinking that some
how it is freeing up the global values and that is what is killing the app.
Thanks,
Hello Group,
Ok, so I debugged it and my thoughts were correct. It is releasing memory
from the globals class. How can I tell it not to release memory from the
globals class? Everything in the globals class is static. Oh, the globals
class is not an activity.
So...if anything in th global
On Tue, Feb 1, 2011 at 8:16 PM, Scott Deutsch surger...@gmail.com wrote:
Ok, so I debugged it and my thoughts were correct. It is releasing memory
from the globals class.
More accurately, it is terminating your process.
How can I tell it not to release memory from the
globals class?
You
Thats what I fearedok I will redesign it to make it work.
Thanks a bunch.
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send
If your process is killed, all the activities are killed so its not
like the globals are released and you still have activities running
causing a force close. Sounds like you need to extend Application()
and use that to contain your static globals. Not that its a good
practice and likely you
Sounds interesting. I should give that a go and see if that fixes my problem
before I totally redesign part of my appi really don't want to do that.
Anyways..any good tutorials on extending Application?
Thanks.
--
You received this message because you are subscribed to the Google
Groups
Extending Application is trivial:
public final MyApplication extends Application {
private Object somethingINeedToCache
}
On Feb 2, 12:56 pm, Scott Deutsch surger...@gmail.com wrote:
Sounds interesting. I should give that a go and see if that fixes my problem
before I totally redesign part
Anything special you have to do in the Android manifest to say that
you over wrote it?
On Feb 1, 9:00 pm, William Ferguson william.ferguson...@gmail.com
wrote:
Extending Application is trivial:
public final MyApplication extends Application {
private Object somethingINeedToCache
}
On
Sorry, yes .. you need to declare it in the manifest too.
See android:name in
http://developer.android.com/guide/topics/manifest/application-element.html
You know Google is a great resources for these types of questions ..
On Feb 2, 3:05 pm, Scott Deutsch surger...@gmail.com wrote:
Anything
12 matches
Mail list logo
