> I had the same feeling Michael, at the moment you can
> name as many objects you want with the same name and
> treat it like a group.

Yup, but one thing missing though with relying on just that for groups is being able to set up some kind of parent/child hierarchy.


> The only thing I can think of is, one object, one name, <...>

One problem with enforcing only a single name per object, is that probably having multiple objects with the same name is going to be useful for certain aspects of polygon mesh exporting, where I will make all objects with the same name get a kind of glued together mesh.


> The way NX 6 handles naming, is with what they call
> categories, we name a category and assign what ever layers
> to it, we either treat it as an individual object or a group or
> a mixture of both.

I'm not quite following how that actually works - for instance what do the layers assignment do to the category? I mean do the layers have an on/off state that controls the category being on/off, and does the color of the layers control the colors of the category?

- Michael