It would be really useful to add input lists to “Create Set” in order to weed them synchronously with the main list, similar to the “Sort list” component.
…wouldn’t it ?
I can imagine a work-around… Would be good to post an example of how that works, eh?
Hi Joseph, I used a workaround of course ; probably not the smartest, but it works.
My point was that it would make this component more useful if it had that extra input/output.
230929_PROG_Create Set improvement.gh (13.5 KB)
I know what your point is, just thought an example would be useful. Here is one, not sure it’s useful?
(white group) Haven’t looked at yours yet.
set_synchronous_2023Sep29a.gh (34.2 KB)
Yeah, I can work around this - but why should I have to?
OOps, You can use the regular Shift path.
Since I use it all the time, I forgot it wan’t a native tool
After looking at yours, I simplified mine. Sure, good idea, though I’m not sure how often I would use it.
Might be useful to export ‘I’ and ‘N’ outputs of MIndex? And flatten (horrors!) the outputs of the B, C and D outputs? UPDATE: Used PShift instead of flatten.
set_synchronous_2023Sep29c.gh (30.3 KB)
Might be confusing to use…
I could do that, or I could output the culling pattern that was used to create the set. That’s a bit more in line with how other components which re-order or remove items from lists operate. Would that work for you as well?
“Culling pattern”? Or ‘I’ (Index) output? See CSet+ cluster in yellow group.
set_synchronous_2023Oct3aa.gh (24.3 KB)
The CSet+ cluster:
Hi David,
Yes, that makes sense.
Sometimes, it doesn’t. I just ran in an example this morning :
231006_PROG_Thats what I want Your love give me such a thrill.gh (19.6 KB)
In specific tools like “Edges from…”, OF COURSE I want a list of edges.
It doesn’t hust to have the indices, sure, but handing over the actual objects that the component advertizes should be mandatory.
“Edges from direction” has both, but “Convex edges” has only got the indices, needing two extra components to get what we obviously want.