http://developer.android.com/intl/fr/guide/developing/debug-tasks.html >Immediately destroy activities > Tells the system to destroy an activity as soon as it is stopped (as if > Android had to reclaim memory). This is very useful for testing the > onSaveInstanceState(Bundle) / onCreate(android.os.Bundle) code path, which > would otherwise be difficult to force. Choosing this option will probably > reveal a number of problems in your application due to not saving state.
On Feb 16, 8:53 am, kk <[email protected]> wrote: > Hi all, > > I've recently done quite a bit of work on saving instance state and > restoring using parcelables for custom data structures. > My problem is that I don't know how to test this functionality on the > emulator. I can trigger calls to onPause and onStop for my activity > (if I navigate out of it) but never onDestroy. So, whenever my app > starts up, it starts with a null bundle. I've never had onCreate with > a non-null bundle and I've never had onRestoreInstanceState getting > called. > > Can someone please tell me how I can test the restore state > functionality from the emulator? > > cheers, > kk. -- 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
