问题
My understanding is that when you change the device orientation, your app gets destroyed and created again. This means that onCreate() should run every time I rotate the device.
I'm trying to set an EditText every time the app is created, including whenever the screen is rotated. So, I start up the app, and the text field says "Bap". I then change the contents of the field to "Boop", then rotate the screen. I would expect the field to now say "Bap", but it doesn't, it remains whatever it was after I changed it, before the orientation change. Why is this?
My onCreate() looks like this:
@Override
public void onCreate(Bundle savedInstanceState)
{
super.onCreate(savedInstanceState);
setContentView(R.layout.main);
EditText editText = (EditText)findViewById(R.id.edit_message);
editText.setText("Bap", TextView.BufferType.EDITABLE);
}
It's worth noting that if I move the setText() call into onResume(), everything works as I would expect it to, with the text field resetting every time I rotate the device.
NOTE: I realize a similar question has been asked, but the answer given doesn't really explain why this behaviour is occuring.
回答1:
It is happening because the Android framework is doing what it is supposed to. It is saving a bundle (SavedInstanceState) with all the information on the current state of your app, to be used when it re-creates your view after the orientation change.
Did you leave some code out of the onCreate you posted? Maybe something like:
if (savedInstanceState == null)
If your onCreate code is wrapped in an if like that, that is why you are not seeing the results you expect.
It is standard practice to have an onCreate that looks like this:
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.main);
if (savedInstanceState == null) {
// Your first time start-up code here, will not run on orientation change
}
// Any code you want to run EVERY time onCreate runs goes here
}
This is done so you don't needlessly re-create everything on an orientation change.
Hope this helps!
EDIT
Looking into it further, it looks like what is happening is this (gleaned from here):
device orientation change
onSaveInstanceState(Bundle outState)
onPause()
onStop()
onDestroy()
onCreate()
onStart()
onRestoreInstanceState(Bundle inState)
onResume()
It's basically saying that the bundle is getting passed to onRestoreInstanceState, which occurs after onCreate, which would explain what is happening in your case.
So, the solution would be to move the setting of the EditText value to your onResume method (or overriding onRestoreInstanceState ).
回答2:
I decided to dig into the savedInstanceState that is passed into the onCreate method, and I found this:
Key: android:viewHierarchyState
Value: Bundle
That bundle had this key, value pair:
Key: android:views
Value: SparseArray
That SparseArray had this value: TextView.SavedState{41857898 start=4 end=4 text=Boop}
So what's happening is that Android is automatically restoring the state of some Views, presumably in the onRestoreInstanceState method.
To prevent this behavior, in XML, add this line to your EditText:
android:saveEnabled="false"
To do this programmatically, call view.setSaveEnabled(false).
回答3:
Yes. When the activity recreated, the edittext can not be set any value in onCreate. you should changed in onResume().
来源:https://stackoverflow.com/questions/10492243/changing-the-value-of-an-edittext-inside-oncreate-has-no-effect-when-changing