I'll have a look into the MarkerClusterer and then also add a fix to the MarkerManager if it suits.
-- Luke On Fri, Jul 9, 2010 at 8:49 AM, William <william.g...@gmail.com> wrote: > a similar issue was reported yesterday, where the V3 MarkerManager has > problems because it doesn't use bounds_changed, but I agree the best > solution is to use a combination of the bounds_changed and idle > events. It would be good if the solution to this problem was used in > both MarkerClusterer and MarkerManager. > > > http://groups.google.com/group/google-maps-js-api-v3/browse_thread/thread/ed9311cd0cdd1723 > > you can report this issue here: > http://code.google.com/p/google-maps-utility-library-v3/issues/list > > ... > > > -- > 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 > google-maps-js-api...@googlegroups.com. > To unsubscribe from this group, send email to > google-maps-js-api-v3+unsubscr...@googlegroups.com<google-maps-js-api-v3%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-maps-js-api-v3?hl=en. > > -- 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 google-maps-js-api...@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
