That confused me completely. On Tue, Mar 31, 2009 at 1:40 PM, Mike Williams <[email protected]>wrote:
> > GMap.prototype.addOverlays was a trick used in the very early releases > of API v1 to speed things up. (The API sorted its internal array of > overlays every time you used .addOverlay(). GMap.prototype.addOverlays > bypassed the individual .addOverlay() calls and only sorted the array > once.) Google fixed the problem quite early in APIv1 by using zindex to > manage the way the markers overlap, rather than sorting them by > latitude. It was still possible to use GMap.prototype.addOverlays in > later releases of APIv1, but using individual .addOverlay() calls was > actually slightly faster. > > In APIv2, the internal array of overlays is not exposed, so > GMap.prototype.addOverlays just crashes. > > Try adding your overlays one by one, and delete > GMap.prototype.addOverlays. > > -- > http://econym.org.uk/gmap > The Blackpool Community Church Javascript Team > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" 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/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
