On Sat, Jul 3, 2010 at 7:42 PM, Indicator Veritatis mej1...@yahoo.com wrote:
That may be true, but if so, there is a serious problem with the
online Android documentation. For as I have already shown, the
documentation clearly states that there is a possible transition
direct from the started
Hi, Mark-
As I should have expected for someone who did write a good book on
Android, I see your knowledge of the Android life-cycle really is
better than mine. But I am seeing something else that vitiates this
superior knowledge, your habit of stating unconditionally, in a very
general form,
On Sun, Jul 4, 2010 at 7:21 PM, Indicator Veritatis mej1...@yahoo.com wrote:
Do you
really want to encourage, for example, Android programmers to fail to
handle correctly the case where onStop() is called without a
preceding, corresponding call to onPause()? Such programming sounds
very
I can do it now!
I finally solve my problem :)
thx 4 the discussion ^^
--
You received this message because you are subscribed to the Google
Groups Android Beginners group.
NEW! Try asking and tagging your question on Stack Overflow at
http://stackoverflow.com/questions/tagged/android
To
This is certainly wrong. Pressing the Back key does NOT cause
onDestroy() to be called. It causes onPause() to be called. I have run
this in the emulator too many times myself to believe that it does.
The application goes into the background, but it remains in memory, on
the activity stack. Only
But what about when the user presses the home key? According to the
docs, onPause() is called WHENEVER the application goes invisible, not
just on the Back key, not just when another application is launched.
So no, it is not just on the Back key.
On Jun 26, 9:13 am, mahesh askmah...@gmail.com
On Fri, Jul 2, 2010 at 2:32 PM, Indicator Veritatis mej1...@yahoo.com wrote:
But what about when the user presses the home key? According to the
docs, onPause() is called WHENEVER the application goes invisible, not
just on the Back key, not just when another application is launched.
So no, it
This is a great discussion.
This is probably the most important aspect of Android. It is critical
for all developers to properly understand activity lifecycle. From the
apps I've seen, most do not.
Google should also do a better job of clarifying and documenting this
lifecycle with additional
That is what the diagram says, yes. But the text of the table says
something different: it says onPause() is called when the system is
about to resume another activity. But it also says that onStop() may
be called when the activity is no longer visible to the user.
More importantly, it says that
That link is a good start, and required reading, but I see they have
still left in the vague and contradictory language concerning which
callback must come next.
I am referring to the wording in the state diagram and the table
concerning whether onStart() or onRestart() are next, and which
ermm... can someone show me or give me an URL that shows how to use
the onDestroy, onPause or onStop??
I am really beginner and didn't understand how systems in Android are
running.
I really appreciate the help
--
You received this message because you are subscribed to the Google
Groups
You are right. It should just be on onPause() and not needed on
OnStop(). My bad...
-
mahesh
On Jun 26, 4:51 pm, RichardC richard.crit...@googlemail.com wrote:
Why both onPause() and onStop()? Looking at theapplicationlifecycle
diagram
http://developer.android.com/intl/fr/guide/topics/fundamentals.html#lcycles
On Jun 28, 7:49 pm, Flamechamp flamechamp1...@yahoo.com wrote:
ermm... can someone show me or give me an URL that shows how to use
the onDestroy, onPause or onStop??
I am really beginner and didn't understand how
And you have to unregister it in your OnPause() and onStop().
Just as ref if you do not know this already -
OnPause() is called when you quit the application via the back button
or start another app.
OnStop() is called when it is actually killed (via task manager)
-
mahesh
Why both onPause() and onStop()? Looking at the application lifecycle
diagram
http://developer.android.com/images/activity_lifecycle.png
it's not possible to get to onStop() without going through onPause().
If however, you have found this not to be the case, I will have to
change my programs
15 matches
Mail list logo
