@Jacob my use of tags in other fields (like photoediting and asset management) doesn’t work like this exactly. I can add 15 tags to a photo and if I filter by any one of those tags, I will find my image. No exact combination of tags is needed to locate it. If we apply this to rhino objects, we could apply numerous tags to a set of objects, which are already on their own layers of course. I use rhino’s naming feature as a workaround for this but would like the ability to give objects multiple discrete names (aka tags) in order to filter and select those objects more easily w/o being limited to the selection tools of the layers panel.
There are tons of reasons we don’t want to clump a bunch of objects onto one layer just to be able to select them easier: material, color, linetype etc. So being able to do the class system you mention that Vectorworks had sounds like a very cool idea to me.
I would like to support this wish as well. And i think this can be simple filtering through excell file. We use microstation in the office for architectural drafting, and the job is done by having all the layers on excell spreadsheet were you save all your layers data under heading that you can filter.
Thank you
I think that tags would work for selection purposes. I was commenting more on the replacement of layers with tags or using tags for visibility. If you’re using tags for visibility lots of tags becomes a nuisance, but having levels could work very well for the exact situation @Constructor described. It would essentially allow sublayers that could be tied to multiple parent layers depending on the object.