Search the Community
Showing results for tags 'auto-classing'.
Found 2 results
-
Why, for instance, are we limited to controlling only the attributes shown in screenshot below? Where is hatch, tile, gradient, image? This seems to make Standard Naming unusable in practice. If I run the Standard Naming command it will overwrite attributes of any existing Classes, therefore limiting one to using Solid Fill colours only....?? What happened here? Was this command created before these other attributes existed?
-
I'm working on building a template file for my firm, and I'm trying to improve our class organization. I've set up a custom naming scheme to use with Auto-Classing, but I'd like to have all of the classes listed in the appropriate column of the "ClassNameStds" worksheet created in the file. Is there a way to do this, or do I have to manually create every class? My goal here is to provide a wide variety of sensibly named classes so that users aren't running around creating lots of additional classes. These classes will all be preset with reasonable lineweights to minimize the amount of post-processing in our viewports (which is currently a lot). I hope that question makes sense. The help documentation and tip videos on auto-classing are ok, but they don't really address this.
