Default display state names on part vs. assembly
Posted: Wed Apr 06, 2022 7:22 am
Anyone know the rationale for why the default display state is named differently in part and assembly templates?
PRTDOT: <Default>_Display State 1
ASMDOT: Display State-1
I tend to rename the display state in my part templates to Display State-1 to match the assembly template and avoid confusing it with the configuration name.
They are both recognized as "the first display state", seeing as the next created display state will be called Display State-2.
And if you rename the display state to Display State-2 you will get Display State-3 for the next one. But if you rename <Default>_Display State 1 to <Default>_Display State 2 you get Display State-1. Logic.
PRTDOT: <Default>_Display State 1
ASMDOT: Display State-1
I tend to rename the display state in my part templates to Display State-1 to match the assembly template and avoid confusing it with the configuration name.
They are both recognized as "the first display state", seeing as the next created display state will be called Display State-2.
And if you rename the display state to Display State-2 you will get Display State-3 for the next one. But if you rename <Default>_Display State 1 to <Default>_Display State 2 you get Display State-1. Logic.