-
Notifications
You must be signed in to change notification settings - Fork 620
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
Delete a single node often results in deleting the entire group #14325
Comments
I find this super annoying as well. I often drop a couple of nodes into a group and want to rearrange them afterwards. Always end up moving the entire group because the selection has changed from the nodes to the group. |
I will echo that myself, looking into this |
tracked internally DYN-6176 |
Thank you for submitting the issue to us. We are sorry to see you get stuck with your workflow. While waiting for our team member to respond, please feel free to browse our forum at https://forum.dynamobim.com/ for more Dynamo related information. |
This has been fixed by #14986 in Dynamo 3.1.0, closing |
If this issue is not a bug report or improvement request, please check the Dynamo forum, and start a thread there to discuss your issue.
Dynamo version
2.18.1
Revit version
2024.1
Operating system
Windows 11
What did you do?
Deleted a node
What did you expect to see?
Node to be deleted
What did you see instead?
Node is automatically added to the group and so the entire group is deleted.
If a node is not in a group ‘properly’ and the node is moved, the node is automatically added to the group. This is expected behaviour. The UX problem is that once added, the entire group is selected, so if you hit delete expecting to delete the node, the entire group is deleted. The solution is for Dynamo NOT to modify the current selection once the node is moved. This seems far more logical to me. Why would I need to select all the nodes in a group?
Refer full disussion here.
The text was updated successfully, but these errors were encountered: