This would have been better off as a new thread.

On Sat, Jun 4, 2011 at 1:20 PM, DulcetTone <[email protected]> wrote:
> The Activity documentation does not clearly indicate the difference
> between an activity being paused versus being stopped.   Is a paused
> activity one which has 1 or more pixels obscured by another, and a
> stopped activity one that has zero visible pixels?

"Paused: Another activity is in the foreground and has focus, but this
one is still visible. That is, another activity is visible on top of
this one and that activity is partially transparent or doesn't cover
the entire screen. A paused activity is completely alive (the Activity
object is retained in memory, it maintains all state and member
information, and remains attached to the window manager), but can be
killed by the system in extremely low memory situations."

"Stopped: The activity is completely obscured by another activity (the
activity is now in the "background"). A stopped activity is also still
alive (the Activity object is retained in memory, it maintains all
state and member information, but is not attached to the window
manager). However, it is no longer visible to the user and it can be
killed by the system when memory is needed elsewhere."

(from 
http://developer.android.com/guide/topics/fundamentals/activities.html#Lifecycle)

IOW, your description is accurate.

> I have never found just where the the interrelationships between
> finish() and state diagram paths toward pause/stop and the use of the
> back  button or home button are detailed.

BACK calls finish() by default, though an activity can override
onBackPressed() to change this behavior.

HOME does not -- it merely brings the home activity to the foreground.

> There seems to be no direct means by which my app (or do I mean my
> task?) can know when one of its activities is active versus not.

Correct, no more than a Web server knows if a Web page is "active" or not.

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy

_The Busy Coder's Guide to Android Development_ Version 3.6 Available!

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to