On Fri, Aug 13, 2010 at 5:04 AM, viktor <[email protected]> wrote:
> OK, I write more clear my issue. > Sorry, but your issue is not any more clear. I have parent activity, other activities extends that. > Extend, in Java, means a class that is a sub-class. I somehow doubt that's what you mean. Do you mean you have an Activity, that starts another Activity? > I want to know when app goes to foreground and after that update > some information in parent Activity. > There is no concept of "app goes to foreground" - you can only have one Activity from your app in the foreground at a time. > If I catch this state with onResume() it is OK for (HW_HOME button), but > if I goes back from child onResume() is appear again. > What state? Why do you need to know how you were brought to the foreground? Why does that matter? > I fully read the Activity documentation, life cycle is good when you are > using single Activity. > Life cycle is perfectly good using multiple Activities if you do it right. > Any other ideas? > Explain what you're trying to do and *why* you're trying to do it. Also, consider reworking your design so knowing how you got to the foreground is not necessary. ------------------------------------------------------------------------------------------------- TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago transit tracking app for Android-powered devices -- 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
