On Nov 18, 2:37 pm, Mark Murphy <[email protected]> wrote: > tatman wrote: > > I'm going through the tutorials about mapview. And it seems like > > there is a lot of "lists" going around and, honestly seems like > > overkill. > > > Is the mapview example accurate in that I need to maintain my map data > > in 3 lists? > > 1) override ItemizedOverlay<OverlayItem> which contains list #1 of > > OverlayItem instances > > 2) ArrayList<Overlay> in my mapviewactivity implementation > > 3) and finally the mapOverlays = mapView.getOverlays(); > > > I'm really confused about all of this. Seems like from a n00b view > > point all I need to do is add overlays to mapView.getOverlays() > > list.... > > 1) represents the points you want on your ItemizedOverlay -- the > push-pins, flags, dots, bowling balls, or whatever you are going to > display for various geographic coordinates. If you do not have this, you > have a pointless (literally) overlay. > > 2) is not necessary. > > 3) is where you tell Android, "Yo, dawg! I gots you a new overlay, yo!" > > In particular, do not confuse Overlay (representing a layer on a map) > and an OverlayItem (representing a point to render in an ItemizedOverlay > in a layer on a map). > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://twitter.com/commonsguy > > Android App Developer Training:http://commonsware.com/training
Thx that does help some. At what point would I have more than one instance of my type derived from ItemizedOverlay, and what point would I have more than one type derived from ItemizedOverlay? It seems like I would keep all of my OverlayItem items in one instance of my type derived from ItemizedOverlay... Matt -- 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
