Multiple edges between cluster and connected nodes #3245
Comments
|
Discussion moved from #3187. First post edited with more info from said issue. Additional from @gubr123 previous discussion: The problem I'm ecountering with clustering is that the nodes are clustered but the edges aren't. So It causes something like this:
I've seen that disabling physics might help, but I don't want to affect the whole network. Is there any option to replace all the edges in one edge? |
|
Analysis: In the code, there was only one hidden edge assigned per clustered edge. The solution is therefore to allow a clustered edges to replace multiple regular edges. This does have some consequences, though. Notably,
|
Fix for almende#3245. This fix adjusts the clustering edges so that theyi can refer to multiple edges instead of just one. This API method is now insufficient, since multiple base edges can be returned. - Added replacing method `clustering.getBaseEdges()` - Adjusted example `changingClusteredEdgeNodes` for the new method. This is the *only* place where `getBaseEdge()` was used - Adjusted documentation for new method and deprecation old method. Method `getbaseEdge()` should now be considered `deprecated`, and in due time should be removed.
* First interim commit * Fixes during testing * Allow multiple edges to be hidden by a clustered edge. Fix for #3245. This fix adjusts the clustering edges so that theyi can refer to multiple edges instead of just one. This API method is now insufficient, since multiple base edges can be returned. - Added replacing method `clustering.getBaseEdges()` - Adjusted example `changingClusteredEdgeNodes` for the new method. This is the *only* place where `getBaseEdge()` was used - Adjusted documentation for new method and deprecation old method. Method `getbaseEdge()` should now be considered `deprecated`, and in due time should be removed. * Edits of method name in example * Edits of method name in example * adjusted deprecation method getBaseEdge() in docs * Adjusted deprecation method for getBaseEdge() in docs
|
I want to cluster multiple edges but not with clustered node(s). Is there a solution yet? I asked here if anyone can help. Thanks. |
* First interim commit * Fixes during testing * Allow multiple edges to be hidden by a clustered edge. Fix for almende#3245. This fix adjusts the clustering edges so that theyi can refer to multiple edges instead of just one. This API method is now insufficient, since multiple base edges can be returned. - Added replacing method `clustering.getBaseEdges()` - Adjusted example `changingClusteredEdgeNodes` for the new method. This is the *only* place where `getBaseEdge()` was used - Adjusted documentation for new method and deprecation old method. Method `getbaseEdge()` should now be considered `deprecated`, and in due time should be removed. * Edits of method name in example * Edits of method name in example * adjusted deprecation method getBaseEdge() in docs * Adjusted deprecation method for getBaseEdge() in docs
As @wimrijnders said:
Simply, the issue is that when two nodes are connected with more than one edge, the edges remain when clustering, instead of creating a 'cluster edge'.
Here is an example of the issue:
Thats I want it to look - (but I want to leave physics enabled):
If I set the physics to false, so all the edges are lapping and it seems like there is one edge between the cluster and the node.
The text was updated successfully, but these errors were encountered: