diff options
Diffstat (limited to 'docs/html/guide/topics/resources/runtime-changes.jd')
| -rw-r--r-- | docs/html/guide/topics/resources/runtime-changes.jd | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/html/guide/topics/resources/runtime-changes.jd b/docs/html/guide/topics/resources/runtime-changes.jd index 871b063..f5475b4 100644 --- a/docs/html/guide/topics/resources/runtime-changes.jd +++ b/docs/html/guide/topics/resources/runtime-changes.jd @@ -32,7 +32,7 @@ alternative resources that match the new device configuration.</p> <p>To properly handle a restart, it is important that your activity restores its previous state through the normal <a -href="{@docRoot}guide/topics/fundamentals/activities.html#Lifecycle">Activity +href="{@docRoot}guide/components/activities.html#Lifecycle">Activity lifecycle</a>, in which Android calls {@link android.app.Activity#onSaveInstanceState(Bundle) onSaveInstanceState()} before it destroys your activity so that you can save data about the application state. You can then restore the state @@ -45,7 +45,7 @@ tasks in your application. Your application should be able to restart at any tim user data or state in order to handle events such as configuration changes or when the user receives an incoming phone call and then returns to your application much later after your application process may have been destroyed. To learn how you can restore your activity state, read about the <a -href="{@docRoot}guide/topics/fundamentals/activities.html#Lifecycle">Activity lifecycle</a>.</p> +href="{@docRoot}guide/components/activities.html#Lifecycle">Activity lifecycle</a>.</p> <p>However, you might encounter a situation in which restarting your application and restoring significant amounts of data can be costly and create a poor user experience. In such a |