Objects or symbol won't move to a different class

[Christopher C Evans]

I just stated a new project, a renovation of an existing space. I can't figure out why I can't move a door or window to a different class such as A-DEMO. When I created a window it automatically goes in the A-GLAZ class. I would like to get it to the A-DEMO. Any thoughts? This has never been a problem in the past.

Thanks.

[Brooklyn]

I didn't have this same problem but another one involving classes. The tech on this board suggesting downloading and installing Service Pack 3.

This cured my problem and might help yours.

Ed

[Jeffrey W Ouellette]

Christopher,

You have "Enable Auto-classing" turned ON. Go to the top menu ->

File > Document Settings... > Standard Naming...

In the subsequent dialog, uncheck the box next to "Enable Auto-classing".

Be aware that this completely turns off the ability of tools to automatically put their objects in the VW predefined classes. You will just have to make changes manually. If you turn it back on, you will get a dialog asking to "reorganize" everything to meet the Auto-classing standards. Be careful of your choice...

[brudgers]

I'll add that for Demo objects it may make sense to convert the high level objects to groups (or primitives) to avoid accidentally reclassing them later.

This is how Alexandria Laundry Lofts is executed, if I'm not mistaken.

[Jeffrey W Ouellette]

Ben,

I turned "Enable Auto-classing" OFF. That way I was able to get the "Demolition" class to stick to doors and windows. The only objects I converted were symbols that had been created with "None" class (e.g. toilets). Those were generally devolved into groups and reclassed.

I just have to be sure that "Enable Auto-classing" is not turned on, thus changing these objects.

I think the best solution would be a move toward "auto-classing" being tool/bject specific, rather than applied to the document wholesale.

[brudgers]

Maybe it was just me then...I remember a demo'd toilet being a 2d poly and some rectangles for windows during my look at the project.

Since there's rarely a need to create before and after models, non-parametric demo info is probably less of an issue...

A toggle which allows classes and layers to be exempt from autoclassing might be enough to manage most situations efficiently...and would allow a variety of workflows.

My first choice would be a toggle for classes...since this is a class conflict.