Simon Brooke wrote:
> In order to bring myself up to speed with Android, I'm trying to get
> this example application:
>
> http://www.helloandroid.com/node/110
Gadzooks, that's old.
> working in Android 1.5. I'm making reasonable progress, and most of
> the API changes I've successfully overcome so far make sense. But one
> class, URLEditor (subclassing Activity), has a method:
>
> @Override
> protected void onFreeze(Bundle outState) {
> super.onFreeze(outState);
> outState.putString("url", mText.getText().toString());
> }
>
> I understand that the purpose of onFreeze was to enable the state of
> an activity to be persisted through a period of dormancy. Is it no
> longer necessary to do this, and if it is still necessary, what
> mechanism does the 1.5 API provide for this?
onFreeze() was renamed onSaveInstanceState().
--
Mark Murphy (a Commons Guy)
http://commonsware.com | http://twitter.com/commonsguy
_Android Programming Tutorials_ Version 1.0 Available!
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
