Hi, You can forward them to the next activity using Activity.onRetainNonConfigurationInstance(). You can also keep static references to the drawables if you remove their callbacks in onDestroy(). You can look at Home's source code for an example of the latter or at the source code of Photostream (code.google.com/p/apps-for-android) for an example of the former.
On Wed, Jan 21, 2009 at 3:49 PM, j <jac...@gmail.com> wrote: > > From reading Romain Guy's blog post, I understand keep static > reference to a Drawable can create huge memory leaks. So what is the > recommended solution if I don't want to reload my big Drawable image > every time screen orientation changes? Currently my app takes >3 > seconds to complete each orientation change. > > > -- Romain Guy Android framework engineer romain...@android.com Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---