> But realistically, what are the special cases when an app would use > android:configChanges="orientation|keyboard|keyboardHidden" to avoid > activity recreation during orientation change?
I think real-time games would use this approach. First, the latency in destroying and recreating the activity would seriously interrupt game play. Also, while I have yet done any 2D/3D graphics, my guess is that changing orientation may be simpler, or at least not reliant upon changing layouts (e.g., res/layout-land vs. res/layout). So, more generically, I would expect to see it in places where the application is not really using the widget-based UI, and hence where the resource change may have no practical impact. -- Mark Murphy (a Commons Guy) http://commonsware.com Android App Developer Books: http://commonsware.com/books.html --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
