Attributes and dictionaries
-
I have a question about using attribute dictionaries/attributes.
I have need to add an attribute dictionary to components, to also add attributes to the dictionary (for example a product code, description, price etc,) and save the changes with the component. I then need to have the facilities to edit these attributes when the components are added to a models.
I do not want to use Dynamic components for this (editing of these is not available in SU Free).
I found a script to add the dictionary and attributes to components, and save them with the component. But I have not been able to find any which allows easy editing of the attributes when the component is later added to a model
Does anyone know of a script which will allow the modifying of attributes (preferably through a dialogue box) for a selected component, and which allows for the change to be saved with the component if required?
-
Thanks kyyu
I have tried that one, but it does not save the added attributes with the component, and the 'Get attributes' does not allow changes.
-
I use this plugin from smustard's site: http://www.smustard.com/script/Attributes
You can use the right click > Attributes > "Get Attributes" feature and just type in a new value. There is a more fancy one, that uses dialog box. But this one, I've found much simpler to use and has just the single rb file.
I'm not sure about saving the attribute with the component? I did a quick test and I couldn't get an imported component to retain it's attribute.
-
What's the plugin that allow attibutes to be save with the component?
'Get attributes' does allow changes. I've used it alot in the past.
-
Try this plugin:
-
kyyu:
The plugin that saves attribute dictionaries and attributes is the one Jim posted.
Jim:
I have this and use it to create and save the attribute dictionaries/attributes.
What I am after is a simplified version of this which only shows the attributes in a particular dictionary in a simpler gui, and allows them to be modified.
If I new how to code I could probably create a modified version of it - but I know nothing about coding.
-
I see the difference. The 2nd plugin applies and reads attibutes to the component definition. Where as the 1st plugin, uses the component instance. It works fine for edges, faces, groups. But for components, they can't see the attibutes set by the other. Also, I don't know if it matters. But if you are changing the definition of a component, then the change is not unique.
Advertisement