spiderified markers collapse every time some markers are added to the cluster

[teo1978]

Consider the following scenario:

• a cluster is created
• as time goes by, more and more markers are added to the cluster
• you start interacting with the map while markers keep getting added to the cluster every once in a while
• you zoom in and you spiderify an icon by clicking on it

Issue: if markers are added while the markers are spiderified, they "unspiderify", meaning they collapse into an icon again. This happens even if the markers that are being added are unrelated with the ones that are spiderified (i.e. they are far away and don't change the number of markers in the "spider").

This is very annoying because it means you just cannot keep adding markers in real time while the user is using the map.

Ajax loading of data that is turned into markers, for example, results in disturbing the user by continuously collapsing the markers that the user is spiderifying.

[danzel]

Necessary evil at the moment. If a marker is added to a cluster that is already spiderfied that would be very bad.
Can probably be fixed with some advanced coding, feel free to have a go :)
(Edit: Woops, didn't mean to close)

[teo1978]

The cluster should be unspiderfied only if a marker is added to that cluster (or subcluster or whatever it is called).
I guess the check could be done at the moment of actually adding the marker to the particular cluster, to see whether that cluster is the one that is spiderfied (as opposed to any other cluster in the group).
I'm afraid I have no idea how to do it myself, sorry.

[teastman]

I've attempted a fix for this. When ever a marker is added or removed it stores a list of spidered markers, then after the clusters are recreated it looks for the cluster containing the stored makers at the current zoom level and spiderfies it.