On Thu, Jun 24, 2010 at 4:12 PM, Raymond Rodgers <[email protected]> wrote: > From everything that I've seen and have been reading, I'm apparently > supposed to add all my OverlayItems in the constructor, then call > Populate().
Not necessarily. You call populate() once you are ready to being responding to methods like size() and createItem(). If your stuff is in a database, you can do your query in your constructor, call populate(), and create OverlayItems in the calls to createItem(). > The problem I have conceptually, is that if I'm pulling these > items from a database (fed by a web site), then when exactly do I update the > items? How do you define "update the items"? > Also, it seems to me that it's a waste of resources to feed it all the items > in advance instead of the ones pertaining to the current location... Then don't feed it all of the items. Also, if you think you have a model that will work more efficiently than does ItemizedOverlay, write an Overlay that uses your custom approach. -- 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
