-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Empty cluster nodes not being removed #3368
Comments
This is a known issue and one I'm very well aware of. Dynamic data update and clustering simply don't play nice together. The changes required for these have been put in motion with #3330, but as I noted in that PR:
I'm actually happy that you reported this, it means that there are more people out there running into this issue, so I can feel justified in handling it with a higher priority. I'll use current Issue as the leading one for these changes. |
Hereby informing you that I'm working on it right now. |
Thanks for the very prompt effort in this and the other issues I have raised since starting work with vis.js. Its is very much appreciated. |
Thanks! Appreciation is the currency for open-source maintenance. I did give this particular issue precedence because I thought it was important. But for this issue, many others have been neglected.....I gave up keeping up 😖. |
Not sure what the intended behaviour is here, but if I have a cluster whose child nodes are removed (externally from the
DataSet
), those objects remain in the network and there does not appear to be a mechanism to reach them programmatically.Example: jbin
The use case is: A network which is populated and updated from an external feed, while clustering is available to the user to manage their view.
My expected behaviour would be to replace a cluster of one node byt its child, and remove a cluster with no children. This issue is compounded by empty clusters not being handled well by the core code, and the lack of any means to iterate cluster nodes in the network.
Workaround may be to cache cluster nodes options and/or ids in
processProperties
to make them accessible to the client code. However this adds a management overhead which duplicates what should be being done within the network.The text was updated successfully, but these errors were encountered: