INTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS

Log In

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Jobs

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:
  • 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..
Now the problem that I can see occurring in the future once I have more "cooks in the kitchen" is that someone is going to accidentally apply a new paint spec to these parts and overwrite all the set up display states.

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?

Instead of using different configurations for the casting and machined parts you should look into Insert Part. This would take the casting (it is a separate part anyway) and leave it as a separate part file, but the machined version would reference it as if it were a dumb solid. This is more representative of the real world, plus it inherently protects the casting from changes done by someone intending to affect the machining only.

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?

(OP)
Appreciate the input! You make a good point about separating the casting from the machining parts. I'll get with the guys here and see what they think.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Eng-Tips Forums free from inappropriate posts.
The Eng-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members!


Resources


Close Box

Join Eng-Tips® Today!

Join your peers on the Internet's largest technical engineering professional community.
It's easy to join and it's free.

Here's Why Members Love Eng-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close