I've seen this happen when someone was forgetting to call superclass methods. If you override onSaveInstanceState, for example, you have to call super.onSaveInstanceState if you still want the default behavior of saving the state of all view's with an ID. There's a similar method in buttons and the like for handling state changes than can be overridden, but then if you don't call the super method the default state changes get ignored, etc..
On Jun 30, 11:16 am, stanlick <[email protected]> wrote: > I have a situation where my input fields are losing their contents. I > have reviewed the sections on saving instance state and believe I have > coded it correctly, however, the problem persists. I actually wonder > if the problem might have to do with a second instance of the > application running as opposed to the original instance being > resumed. The reason I say this is because I have seen times where my > application presents itself as an empty page and hitting the "return" > button displays my application with all the data as it had been > entered. Can you tell me more about the manifest entries concerning > android:alwaysRetainTaskState="true" > and/or android:launchMode="singleTask" Also, I discovered an > attribute on the EditText control called android:saveEnabled="true". > > Can you assist in clearing up this seemingly trivial use case? > > Peace, > Scott -- 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
