You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 16, 2019. It is now read-only.
Could you also elaborate what problems we get without clusteringbegin and clusteringend?
This will give possibility to handle events for visible set of clusters only, ex: better performance
// Adding preloading for visible clusters MapPropertyCollection.prototype.bindClusterEvents=function(){var_this=this;google.maps.event.addListener(this.cluster,'clusteringend',function(){_this.preloadPreviews();});};// And later, show cached image on mouse overgoogle.maps.event.addListener(marker,'mouseover',function(){infoWindow.open(_this.map,this);_this.showPreview(marker);});
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Clusters are missing classes which makes impossible to operate(work) with them, like change the opacity of all clusters.
It can be solved by adding class variable programmatically on
tilesloaded
gmaps event, but there are cases when this is not working properly for this "js-marker-clusterer".So I will much better to have separate events
clusteringbegin
&clusteringend
,similar to: https://github.com/googlemaps/v3-utility-library/blob/master/markerclustererplus/src/markerclusterer.js#L1491 & https://github.com/googlemaps/v3-utility-library/blob/master/markerclustererplus/src/markerclusterer.js#L1536
along with class attribute for a marker
The text was updated successfully, but these errors were encountered: