Hi JTB, yeah I think it should be able to work with imported traditional "layer" data from AutoCAD (or actually Rhino's layers are the same too).
I mean there will be a lot of similarities to layers, it will be a way to assign objects to a certain kind of "tag" which is kind of the basic element of how layers work.
The main difference will be that you won't be forced to only assign an object to a single "tag", which is normally the big limitation with traditional layers where each object has a property of which layer it is on, and it can only be on just one.
I'd like to make it so that objects can belong to different "tags" instead of only just one.
With a little bit of additional support in the UI I think this same method will work for grouping - a group would be a tag that you create and then set an option on the tag for "Select as one".
Also somewhere in the UI I'll try to make it easy to click something to select all the objects on a certain tag - I think that should let it work as a named selection set as well.
So the idea is to have something more flexible than layers, and also incorporate named selection sets, and grouping all in the same interface instead of as totally separate concepts.
- Michael
|
