-
-
Notifications
You must be signed in to change notification settings - Fork 98
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
Allow editing groups with multiple nodes selected at the same time #10331
Comments
I would add that the removing of the scene manager is a regression. |
As a bit of a note, for your particularly huge struggle you could write a short EditorScript. It would go through the edited tree and, on each node of interest, call |
Adding support for this. There's plenty of use cases for wanting to select more than one node at a time and edit the group assignments as a batch job. |
This comment has been minimized.
This comment has been minimized.
@ugothmeex Please don't bump issues without contributing significant new information. Use the 👍 reaction button on the first post instead. |
Describe the project you are working on
A panda torturing game
Describe the problem or limitation you are having in your project
I've got 130 copies of the same node, each positioned manually, and to get all of them in an array I want to add them to the same group but it is a total pain to go over each copy and manually set the group
Describe the feature / enhancement and how it helps to overcome the problem or limitation
There should be a way to change groups on multiple nodes at the same time
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams
By selecting multiple nodes in the editor, you should be able to set groups to all of them like how you can do with exported boolean variables in the inspector
If this enhancement will not be used often, can it be worked around with a few lines of script?
In some cases you can by adding nodes to group via script, that's how I think I will solve the problem I previously described, but in other cases you might not be able to do it
Is there a reason why this should be core and not an add-on in the asset library?
An add-on has to be installed for every project, and I'm not even sure if you can implement with one of them
Sorry for any grammatical errors
The text was updated successfully, but these errors were encountered: