You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I find my self currently testing Nodes and also different implementations of Nodes, and i don't want to have multiple implementations of the Nodes running at execution of the Tree, and i don't want to delete them for conveniance if they have many In / Outputs i would need to refill if i want to test the other node again.
Describe the solution you'd like
It would be nice to simply right click the Node and deactivate it. In Case of Sequences deactivate the whole sequence and so on.
Would be nice if the Node then is visually greyed out or something.
Describe alternatives you've considered
I could pack the Node in a Subtree and therefore don't lose the Information if i remove the subtree but that creates quickly deep trees
Groot Version 1.5.2
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I find my self currently testing Nodes and also different implementations of Nodes, and i don't want to have multiple implementations of the Nodes running at execution of the Tree, and i don't want to delete them for conveniance if they have many In / Outputs i would need to refill if i want to test the other node again.
Describe the solution you'd like
It would be nice to simply right click the Node and deactivate it. In Case of Sequences deactivate the whole sequence and so on.
Would be nice if the Node then is visually greyed out or something.
Describe alternatives you've considered
I could pack the Node in a Subtree and therefore don't lose the Information if i remove the subtree but that creates quickly deep trees
Groot Version 1.5.2
The text was updated successfully, but these errors were encountered: