Hi Mark, It's only causing a slight annoyance to the user. Although the UI takes about 1.5 seconds to completely build, I am doing a staggered load. This lets the user see content immediately, but they're wondering why every time they leave the search activity, then come back, all the content must be reloaded. The actual search data is kept in a global static singleton, no problem there, just the UI is kind of heavy to keep regenerating around it.
This would work better as a tabbed-view in a single Activity, but my spec calls for the search screen to be in a separate Activity. I like keeping it separated too, just wish I could pause the app to resume it later since I'm sure it's an Activity users will keep coming back to while using the app. Thanks On Nov 23, 12:55 pm, Mark Murphy <[email protected]> wrote: > Mark Wyszomierski wrote: > > If after its first construction, I could just request it be paused > > instead of destroyed on the back button, then I could reuse it. Is > > there a sensible way of doing this? > > Is it causing you particular problems? If you are not experiencing > problems, this feels a bit like premature optimization. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://twitter.com/commonsguy > > _Beginning Android_ from Apress Now Available! -- 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
