drgreen/android_frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge "Fixed typo in Recreating an Activity documentation"

Browse Source
This commit is contained in:
Amith Yamasani
2013-01-02 09:00:28 -08:00
committed by Gerrit Code Review
parent 5cb0f21846 870d2a2988
commit 554ed0f034
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/html/training/basics/activity-lifecycle/recreating.jd
View File

@ -39,7 +39,7 @@ resources so the system must shut down background processes to recover memory.</
<p>When your activity is destroyed because the user presses <em>Back</em> or the activity finishes <p>When your activity is destroyed because the user presses <em>Back</em> or the activity finishes
itself, the system's concept of that {@link android.app.Activity} instance is gone forever because itself, the system's concept of that {@link android.app.Activity} instance is gone forever because
the behavior indicates the activity is no longer needed. However, if the system destroys the behavior indicates the activity is no longer needed. However, if the system destroys
the activity due to system constraints (rather than normal app behavior), then althought the actual the activity due to system constraints (rather than normal app behavior), then although the actual
{@link android.app.Activity} instance is gone, the system remembers that it existed such that if {@link android.app.Activity} instance is gone, the system remembers that it existed such that if
the user navigates back to it, the system creates a new instance of the activity using a set of the user navigates back to it, the system creates a new instance of the activity using a set of
saved data that describes the state of the activity when it was destroyed. The saved data that the saved data that describes the state of the activity when it was destroyed. The saved data that the