On Thu, Jun 24, 2010 at 5:09 PM, Raymond Rodgers <[email protected]> wrote: > or from background actions such as receiving new items from > the server?
It looks like you can just call populate() again, based on some sample code a subscriber sent me (on an unrelated issue). However, I have not played around with this specific scenario much. > I'm one of those programmers that always tries be mindful of the amount of > memory being used, and although I don't think my app is going to be a memory > hog or need to have millions of points on screen at any given time, I also > don't want to populate the overlay with items in Florida when the map is > centered over Hawaii. It was my intention to just load the data necessary > for what's currently visible to save memory and improve performance overall, > but based on what you've told me, maybe I should take another approach. I'm just saying that the authors of ItemizedOverlay would not appear to be worried about the issue. Hence, I'd wait until you see concrete problems. Premature optimization and all that. Your way of thinking is delightful, though. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android App Developer Books: http://commonsware.com/books -- 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
