On Mar 16, 6:03 pm, Scott H <[email protected]> wrote:
> I am working on migrating my API v2 code to v3. My mapping solution
> requires a good amount of markers to go on the map at one time and, with
> version 2, I utilized the MarkerLight. This offered MUCH better performance
> because it was merely adding an image overlay onto the map without all the
> weight of other objects info.
>
> Looking at version 3, it appears that Google has really tried to solve the
> need for using extensions like MarkerLight and made the standard markers on
> maps much much faster.
>
> Can anyone confirm this via their experience in loading lots of points onto
> a v3 map? I have read the documentation and know it says it works well, but
> I am curious of anyone's actual experience with it especially if you went
> through a similar transition from v2 to v3.
>
> Thanks!
Last post appears to be lost. Sorry if it is a duplicate.
Google has addressed the display aspect. Unfortunately, hundreds or
thousands of similar markers still require hundreds or thousands of
event listeners. For reasons to not use "function closures", see:
http://groups.google.com/group/google-maps-js-api-v3/browse_thread/thread/2a2c2cbaf273d5d3#
--
You received this message because you are subscribed to the Google Groups
"Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
