Thanks for the input.. I ended up just saving out my data from the pull as suggested, it was already an ArrayList and I just jammed it in with the putSerializable and it works fine.
Thanks for the help guys. On Oct 10, 10:26 am, Mark Murphy <[EMAIL PROTECTED]> wrote: > Mark Hansen wrote: > > The list is pulled from a remote feed over the web, so I was trying to > > prevent having to reload the listview via another web pull. > > I would recommend storing the data from the feed somewhere other than > just in the ListView itself. Database, XML file, JSON file, whatever. If > you go with the database option, you can use a CursorAdapter and still > only have one copy of the data -- just in a spot that is designed to > live longer. > > > Basically I just want the application to save everything and then > > restore itself when the user changes orientation, instead of having to > > make another full call back data source. > > Understood, but I suspect the instance-state mechanism isn't designed > for large data sets. > > -- > 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 -~----------~----~----~----~------~----~------~--~---
