Any way to "idiot-proof" display states?
Any way to "idiot-proof" display states?
(OP)
Howdy all,
So in my situation I have a series of parts in an assembly that can be described using the configuration and display states shown below:
So I guess I have two questions:
(1) Has anyone found a better method than this to have control of different appearances of display states?
(2) Has anyone found a way to "lock" display states so we don't have the potential of overwriting all display states when someone adds another color into these parts?
We do use PDM, if that helps at all.
Thanks!
So in my situation I have a series of parts in an assembly that can be described using the configuration and display states shown below:
- Configuration #1 - CASTING
- - - Default display state
- Configuration #2 - MACHINING
- - - Default display state showing only the machining that has been done to the casting
- - - RAL Paint spec #1
- - - RAL Paint spec #2
- - - RAL Paint spec #3
- - - etc..
So I guess I have two questions:
(1) Has anyone found a better method than this to have control of different appearances of display states?
(2) Has anyone found a way to "lock" display states so we don't have the potential of overwriting all display states when someone adds another color into these parts?
We do use PDM, if that helps at all.
Thanks!






RE: Any way to "idiot-proof" display states?
As far as display state control goes, I don't often use them in my work, but I have seen people use an assembly of only one part where it is colored/painted in that assembly. They did this a couple of different ways: One is to have a separate assembly for each color as in Part-red.sldasm and Part-Green.sldasm, and another where they had different configurations controlling the different colors.
I hope this helps.
- - -Updraft
RE: Any way to "idiot-proof" display states?
RE: Any way to "idiot-proof" display states?
Regards,
Jon
RE: Any way to "idiot-proof" display states?