Because that's what a smart person would do & I'm an idiot for not thinking about it before asking <grin>. That's two whacks -- I'm outta here.
Need more caffeine... Cheers, tim On Feb 2, 3:10 pm, "Mark Murphy" <mmur...@commonsware.com> wrote: > > There's still the lifecycle handling -- if I have this ArrayList, and > > I want to keep it across rotates, I could keep it in a static. The > > trick is knowing when to release/null it. First thought is to set a > > flag in onRetainNonConfigurationInstance, otherwise I'll release it if > > the flag isn't set when onDestroy comes along. Seem reasonable? > > Why not just pass the ArrayList in onRetainNonConfigurationInstance()? > > -- > 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