-
-
Notifications
You must be signed in to change notification settings - Fork 368
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setting cluster fixed option doesn't do anything in hierarchical layout #179
Comments
I'm not exactly sure what you're trying to achieve. Could you provide more info, please? |
I am trying to be able to move the nodes freely and not only on one axis. |
So disable hierarchical layout. The whole purpose of this layout is to prevent what you're trying to do. |
Just to give you some more context, we're using the hierarchical layout for positioning because it is the most visually aesthetic option in our use case; however, we would like to allow for moving nodes around on both axes.We managed to make it work by unsetting Enabling and Disabling the hierarchical layout has the issue I posted earlier #178 |
Yeah, I understand what you're doing. The problem is that hierarchical layout is not supposed to be used in this way. |
Experiencing the exact same issue. I want the hierarchical layout on initialization, but after that, I want the nodes where they can be freely positioned by the user (I have physics off). I've achieved this with the same approach of disabling |
I'm using the hierarchical layout, and on node dragStart I update the node fixed property to
While this works for non-clustered nodes it doesn't seem to work for clusters.
Here is a codepen example
The text was updated successfully, but these errors were encountered: