Brandon PT Davis
Menu
Studio
Getting started tutorial gradient
Tools & Technology

Understanding Classes

By Brandon PT Davis

Learn how classes control object appearance, attributes, hierarchy, and visibility across a scenic drafting file.

A strong class system lets a file stay visually legible even as the drawing becomes dense. Line weights, fills, textures, and visibility can be managed consistently instead of adjusted object by object.

Scenic drafting depends on that control because drawings mix architecture, dimensions, scenic objects, masking, notes, and 3D elements. Classes let those categories behave predictably across views.

Use class names as structure

Hyphenated class names create hierarchy, so related drawing categories can stay grouped and searchable.

Class names should describe graphic purpose, not only object type.

Graphic standards

Classes are visibility and attribute rules, not geometry containers.

Layers hold drawing context. Classes control how objects look and whether they can be seen across views.

HIERARCHY

Use names to keep categories readable

Hyphenated class names create a structure that can be scanned, filtered, and taught.

ATTRIBUTES

Let Use at Creation carry the standard

Line weight, fill, texture, and line type become class behavior instead of memory work.

GROUPS

Grouped objects still keep class behavior

A group can contain objects that respond differently when class visibility changes.

Class hierarchy

Class naming hierarchy

See how hyphenated names group related classes and make a file easier to scan.

  • S-Ground Plan
  • S-Walls
  • S-Trim
  • Dimension

Class attributes

Class-controlled or manually overridden

Check the difference between an object that follows class attributes and one that has been manually styled.

  • Class-controlled objects revise globally.
  • Manual overrides can hide drafting standards.
  • Visibility can be managed without moving geometry.

One guiding idea

“Classes make a drawing easier to trust because graphic standards stop depending on memory.”

Classes describe graphic behavior

A class is not a place where an object lives. It is a set of graphic and visibility instructions that can travel with that object across the file.

That difference is what separates classes from design layers. Layers organize drawing planes. Classes organize how objects appear and whether they are visible in a given view.

Use at Creation keeps standards intact

When class attributes are used at creation, an object can inherit the correct line weight, fill, color, texture, or visibility behavior automatically.

That makes the drawing more consistent and easier to revise. Instead of selecting dozens of objects to fix a graphic standard, the class can carry the standard for the whole category.

Supporting material

Shortcuts

Cmd / Ctrl + G
Combine multiple objects while preserving their individual class assignments

Keep in mind

  • The five-square demonstration transcript is brief, so avoid inventing missing steps.
  • Modeling in None is a Brandon workflow standard and should be framed as such.

Potential exam questions

Apply the workflow to a drawing problem. Use these cards for study or discussion, then revisit the demonstration when you need context.

Question 1 of 2

You want overhead linework organized into a nested class list. Which naming pattern creates the hierarchy demonstrated in the lesson?

  1. 2D Overhead Dash
  2. 2D/Overhead/Dash
  3. 2D-Overhead-Dash
  4. 2D_Overhead_Dash

Understanding Classes

Continue reading

Related articles