Projecting list item numbers on corresponding object

I want to deconstruct a poly surface with many surfaces (lets say 100) and I need to group them as sets to achieve that I make sets and selecting parts by of it by trying out from number slider is it possible to project list item numbers on corresponding items, so selection would be easier?*


*

Try this instead:


I cannot say I did understand your solution I don’t really understand which nodes that you use. I do not have familiarity with these, can you share the file?

It’s in the other thread. vuTreeList_2017_Jan19a.gh (20.0 KB)

Connect your Deconstruct Brep ‘F’ (Faces) output to the vTrE input. The ‘path idx’ slider will have no effect if there is only one “branch” (Brep in this case) but if you have multiple breps, each one will be a branch. The ‘list idx’ slider will cycle through the list of faces in each branch.


As far as I understand it is splitting geometry to branches so makes it easier to reach the desired geometry by adding a branch layer on them. However, I have set of surfaces did not work really well. Thanks for the help anyway

Uh… no. The number you see in the yellow text panel (35) is the position in the list (branch) of the highlighted (yellow) face. It’s the number you asked for, just not “projected” onto each face.

Oh then there must be misunderstanding, I dont want to see the corresponding numbers one by one on slider but on top on surfaces on the rhino geometry, so I can immediately know which number belongs to which face just by looking the geometry. Sliding through numbers causing too much drudgery when there is too many faces they have to be identified in different sets.

maybe something like that

1 Like

Yes something like this, but I really don’t know which nodes you did use they really mean nothing to me without their names. What is the square node at top left?

No misunderstanding. I offered a general purpose tool that I have used everyday for years. It works well with data trees of breps, surfaces, curves, points, whatever - geometry that may not be suitable for numbering as as you suggest. Among other things, I use it to create lists (“sets”) of edge indexes that are passed to Fillet Edge, selecting only some edges, not all.

I don’t see any difference in drudgery when you are creating such lists (“sets”) manually anyway?

It’s possible to create such lists in other ways too, automatically, using proximity to points or curves or sorted by position. Your mileage may vary.

By the way, you didn’t post any code or geometry so it’s customary to respond in kind, with only images instead of more useful GH files.

Here is model that lets you select/toggle a list of geometry: