On Mon, Jul 19, 2010 at 10:16 AM, Jin Chiu <[email protected]> wrote:
> Is there an exception in the lifetime rules for a parent activity that's > in the background after invoking startActivityForResult()? > Not that I'm aware of. >From my understanding, in low memory scenarios, the background activities > are killed before the foreground. > Right. > Does this rule still apply even if the background activity started the > foreground one for the purpose of obtaining some result? > I believe so. In this case, I think it would make sense for the foreground child activity > to get killed first or to equalize the lifetime of the parent and child. > No, that does not make sense. So user starts activity A, then does something to launch activity B from A. Now they are working in B and low memory hits. You think it would make sense for Android to kill B, the activity the user is using in this case? Why is this a problem for you? ------------------------------------------------------------------------------------------------- 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
