I've updated the MarkerClusterer to cluster on idle now, but the user experiences is a bit worse because it does the clustering when the user has finished dragging so they will notice the clustering happening.
I could do something like cluster on bounds_changed if there is less than X markers where X can be defined in the constructor, but I will wait to see what people want before I do something like that :) -- Luke VP, Keepin' It Real On Fri, Jul 9, 2010 at 10:03 AM, Luke Mahé <[email protected]> wrote: > 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 <[email protected]> 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 >> [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<google-maps-js-api-v3%[email protected]> >> . >> 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 [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.
