Rmac wrote: > Why not have an option to tell Android there is no need for an > activity recreate if there are no alternate resources?
Somehow, I think you're missing the point. The code you are trying avoid (saving/restoring instance state), you need anyway. So just write it. If you don't, your application will not work in production, when real people use your app on real devices with real memory restrictions that cause your application to go bye-bye at random times. The mere fact that one of those "random times" is when the user slides open the keyboard should matter not a whit. Your app could go away just as easily because the person took a call, then started to play Super Orangutan Spheres for a while, and orangutans make lousy Java coders, so there's a memory leak, which eventually causes your application to get ejected from memory. Or, they realize they needed to look up something else while using your application, got distracted, forgot all about your app, and eventually enough other stuff gets done that causes your application to get ejected from memory. Or any number of other combinations of events. So, if you need to support saving/restoring instance state to have a meaningful application in production, just write the code and be done with the matter. You wind up with portrait/landscape handling "for free". -- Mark Murphy (a Commons Guy) http://commonsware.com _The Busy Coder's Guide to Android Development_ Version 1.3 Published! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
