Like in “other software”, it would be very useful, particularly for collaborative work, if Rhino would automatically name and number each entity, so one can keep track of what tool was used to build it.
Hej -
So what happens when you then cut a hole in that surface? Does the name automatically change to trim_#9477234?
-wim
It’s not uncommon to work with thousands of surfaces. This list will not help with anything, it’s meaningless. I doubt anyone can can even demonstrate it works in history-tree-based software where there is actually a hierarchy to display that’s actually part of the model.
An object lister is very useful, which is why Alias, Maya, Plasticity, Blender, etc. have something like it, to organise objects, toggle visibility, symmetry, etc, organise complex models for collaborative work, query an object’s history, etc. You may doubt it, but all users I have trained or worked with use it.
In any case, that issue is beside the point. Wim wanted to know about the trimmed status of a surface. The point was and is that Rhino should feature automatic entity naming instead of leaving the name field blank.
Hej @wim here’s a typical example of many, where automatic entity naming would have been useful. Now think of three people working on a new dentist’s chair or combine harvester, or someone who comes back to a project after a week and might have forgotten what was used where.
Hi @Lagom,
We’ve had similar request to this in the past. I’ve logged your wish - https://mcneel.myjetbrains.com/youtrack/issue/RH-93855.
That said, what you’ve show can be done by a motivated plug-in developer. Our SDKs provide all the tools to do this.
– Dale