onSaveInstanceState与onRestoreInstanceState

最新推荐文章于 2024-11-28 05:03:04 发布

Snowball

最新推荐文章于 2024-11-28 05:03:04 发布

阅读量834

点赞数

分类专栏： Android 文章标签： interface hierarchy initialization user each resources

Android 专栏收录该内容

72 篇文章

订阅专栏

本文介绍了Android中Activity如何通过onSaveInstanceState和onRestoreInstanceState方法保存与恢复状态，确保在系统资源回收后能够还原用户界面。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

protected void onSaveInstanceState (Bundle outState)

Since: API Level 1

Called to retrieve per-instance state from an activity before being killed so that the state can be restored in onCreate(Bundle) or onRestoreInstanceState(Bundle)(the Bundle populated by this method will be passed to both).

This method is called before an activity may be killed so that when it comes back some time in the future it can restore its state. For example, if activity B is launched in front of activity A, and at some point activity A is killed to reclaim resources, activity A will have a chance to save the current state of its user interface via this method so that when the user returns to activity A, the state of the user interface can be restored via onCreate(Bundle) or onRestoreInstanceState(Bundle).

Do not confuse this method with activity lifecycle callbacks such as onPause(), which is always called when an activity is being placed in the background or on its way to destruction, or onStop() which is called before destruction. One example of when onPause() and onStop() is called and not this method is when a user navigates back from activity B to activity A: there is no need to call onSaveInstanceState(Bundle) on B because that particular instance will never be restored, so the system avoids calling it. An example when onPause() is called and not onSaveInstanceState(Bundle) is when activity B is launched in front of activity A: the system may avoid calling onSaveInstanceState(Bundle) on activity A if it isn't killed during the lifetime of B since the state of the user interface of A will stay intact.

The default implementation takes care of most of the UI per-instance state for you by calling onSaveInstanceState() on each view in the hierarchy that has an id, and by saving the id of the currently focused view (all of which is restored by the default implementation of onRestoreInstanceState(Bundle)). If you override this method to save additional information not captured by each individual view, you will likely want to call through to the default implementation, otherwise be prepared to save all of the state of each view yourself.

If called, this method will occur before onStop(). There are no guarantees about whether it will occur before or after onPause().

Parameters

outState	Bundle in which to place your saved state.

protected void onRestoreInstanceState (Bundle savedInstanceState)

Since: API Level 1

This method is called after onStart() when the activity is being re-initialized from a previously saved state, given here in savedInstanceState. Most implementations will simply use onCreate(Bundle) to restore their state, but it is sometimes convenient to do it here after all of the initialization has been done or to allow subclasses to decide whether to use your default implementation. The default implementation of this method performs a restore of any view state that had previously been frozen byonSaveInstanceState(Bundle).

This method is called between onStart() and onPostCreate(Bundle).