I frequently have to split or retrieve many branches of a trees with the exact same path structure. I then have to rewire and reuse many components, whereas it could have been as simple as pressing a (+) to get a new Data/ Tree input. Please add these kinds of options to save me some work and to ease reading the script (because now I have to track the in and outputs and all the wires start to create a mess fairly easily).
No gh files atached
I sort of understand what you mean, but I’m having difficulties understanding how the right side (output) of the component would be in case multiple inputs are present
for instance, if you have 2 inputs, with 2 different data trees (of course with very same data structure) would you also have respective/dedicated P/N outputs for each tree?
like you have a single DataTree input and two P,N outputs
the moment you click the + to add a second Tree input you would get a new couple of P,N outputs for that tree?
I would consider that as painful as having multiple components copypasted next to each other, with the added downside that input/output alignment wouldn’t help either:
because otherwise you can do something like this, and organize the whole thing into a single data tree, and filter the different beanches simultaneusly as if they were one:
split_tree_inputs_inno.gh (12.8 KB)
but to be fair I have some doubts how this compound_&_filtered data tree would be useful for any further use without being isolated-back into its initial components
Personally, I would group all the Positive and Negative outputs together.
So:
Positive 1
Positive 2
Positive 3
Negative 1
Negative 2
Negative 3
As for the compound tree, there should be an Unentwine component to isolate the tree back to its initial components.