Similar to the Config/Custom Property
Anyone know what the "sw-custom property" code is to get the name of the display state as a custom property
If you fly out the display states panel and RC on the display states
icon you can add a display state. Then if you already have configs and
a design table it will add $display states to your table.
Hi scott - what i got in the email confirmation and what's posted seems completely different.
Kind of, i just need a custom property field which would show the display state that has been selected to be shown. So that if someone was looking at an assembly report or a they could without opening it would know what the name of the display state is. (ie a colour).
Yeah I did some research after my original posting and changed it up a little.
I know in drawing templates the coding is like $PRPSHEET:"value"
If you looked at the design table attachment I gave you it says $DISPLAYSTATE
then the value says "Display State-6" The number representing which state.
So I am thinking $DISPLAYSTATE:"Display State-6"
haha, ok i thought i was going mad.
yeah i thought exactly the same when i saw the name of the colum $displaystate
I tried the following "codes" in the custom property field
$PRP : Displaystate
$PRP :"Display state"
still to no avail!
so i thought i had cracked it looked at the actual dispay state box (which is attached)
$PRP:"Display State name"
"Display State name"
$"Display State name"
"Display State name@Part1.SLDPRT"
and guess what.....
still no luck..
The bigger question might be "Can display states be specified in custom properties?"
In the research I have looked for I am not seeing that it can.
Can you do a work around by using the design tables in conjunction with configurations?
i added a edit to the above with some more options that failed
We have just moved from using colors defined by configuration to defined by display state. so really it would be a step back i think?
If the display states cannot be specified in custom properties then time for a enhancement request!
That is your call as to whether it is a step back. Depends on your application.
The more I think about this what comes to mind is custom properties are all about
adjusting or applying values. Display states are strictly visual.
Maybe it is time for an enhancement request. Not going to argue that it wouldn't
be needed or wanted. If we had our ideas portion back that would be a telling sign.
ill have another go tomorrow, thanks for your input scott. Its more of a tracablity tool, Within our production if we have 1 component available in lots of colours but there under the same part number at the moment. Just a custom property for the MRP system to look at would be ideal to identify what is supposed to be used.
I am actually looking into a few things that I want to see if they will work.
One thing I just thought of is, if you know how to create/update a material file (.sldmat)
do a save as of the existing one, and create a materials for all of the different colors you need
by changing the display states for each of them in the material dialog window.
Then link the material to a custom property. I know the material can be linked to a custom
property because I have done it.
This might sound like a crazy idea, but I think it might work. Unless you have thousands
of different colors then time could be a factor.
Still looking into other things though.
I would say this is inherently impossible (although I can't prove that).
There can be multiple display states, and they may or may not be tied to any configuration.
There is only one custom property tied to any configuration.
Thus, it might often be wrong.
but the display state could be non-configuration specific just to confuse the situation even more.
Somehow the custom property would have to look at what the Name of each selected display state for each version was, much like a configuration, but I was lead to believe that display states are alomst a configuration for colors.
so im not sure, i dont know enough about soildworks, configs or displaystates and so on.
Still if anyone has any ideas, im listening!
Did you happen to see my idea about the material file in my last posting?
No sorry I missed that Scott, but i see yeah that would work i guess.
unless that part was one color all the time you would have to have different colors saved.
the way you could get around this is to have config with the different material colors... but then you just may as well have config controlled colors, which display states was trying to get away from.
It might be if they want this kind of tractability they have to have more then one configuration of each configuration for each color - which completely defeats the point of display state.
I agree, which means in this discussion, you are coming around full circle.
Right back to where you started.
Sorry I couldn't help more. Good luck with this.
Retrieving data ...