Thanks Mark. > Use the LIMIT and OFFSET terms on your SELECT statement to obtain data in > smaller chunks. Create a wrapping adapter (like my EndlessAdapter) that > only loads chunks when the user scrolls to the bottom of thelistand > therefore needs more data. >
Doing the load in smaller chunks would still require at least the same amount of time to fill the list, but it would let me interrupt the load more quickly, so I can incorporate that & handle rotates normally -- thanks for the whack on the side of the head! Unfortunately, I still need to load the full set of records because I need to be able to provide a sliding window anywhere in the result set, not just add to the end of the the list during the load (i.e., the user is not just continuously scrolling to the bottom of this huge list). Similar to a scroll button in typical windowing systems, in this list of events & timestamps, the user needs to be able to select a position, say 2/3 of the way down the list & scroll to the entries they want to review. Is the list/adapter just creating 20K objects as it walks the result set? If so, I'd be tempted to do this myself so I can give the user some visual cue/index into the data. I don't want to add significantly more overhead though. Any additional suggestions/insights? Thanks again, Tim -- 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
