I would like to request a feature where Attributes can be added to objects by layer, the way we apply Materials to objects by layer. The reason I ask this is that whenever I want assign my custom Attributes.csv to objects, I would have to select each and every object and Import the text or use the Match Attributes command and click an object with an attribute to match.
This is quite cumbersome and time consuming especially if I continue to create new objects that has to have my Attributes. Why canāt we just :
Import/load our Attribute User Text and let Rhino save it in a list or dropdown list in a panel.
Have the additional option to Assign it By Layer, Object, etc.(The way we assign Materials)
Have the option to Filter by Object Type so that my custom Attributes would only be assigned to specific object types of my choosing i.e. a Curve, Point or Brep.
This system can speed up modeling especially when workflows depend on grasshopper attribute extraction (Elefront, Human, Heteroptera etc.)
It would be good to get a better understanding of your workflow first. You are mentioning the objects need to be processed in grasshopper later on. If that is the case, you could make rules in grasshopper that assign those attributes based on object layer and type.
Thanks for replying. The workflow Iām talking about is starting from native rhino commands. In this environment we all know we can add attributes to objects. But itās tedious especially when it comes to creating new objects when doodling with curves , breps etc. Creating a new geometry entails me to click on the attributes tab again and click on the match attributes command and then click again to an existing geometry with said attributes. I think a better way is what I mentioned where we can just import all the User Attribute Text files we made; store it in the panel as a dropdown list (Like a material list), then when need be i could just apply it to an object, layer etc. The thing with grasshopper is a few steps down the line. Iām focusing on the native rhino UI.
For instance I have a phase attribute for a different buildings in a masterplan. I just run an alias called āPhaseā and type the phase number.
-_SetUserText phase
Or if you know you are only going to need lets say 3 phases then you can just make 3 aliases of Phase1, Phase2, Phase3.
-_SetUserText phase 1
This has been working well for us without having to touch grasshopper yet for automating the user text.
I donāt understand what aliases have to do with my request. Iām asking for an extremely easier way where we can apply our User Text Attribute like a material. Like below:
That way, every geometry I create on that layer automatically inherits the User Text Attribute. No more extra clicking, no more Aliases. Itās basically how BIM Softwares operate, where Attributes (Parameters) are stored and are easily accessible and assigned to objects that are filtered either by type, layer, etc.
Attribute texts are object properties. Layers are too in fact. Assigning it based on layer is not 100% straightforward therefore. What would you expect to happen to the attribute once the object moves to another layer?
Then I would expect the attributes to update and inherit the Attribute of the new layer, if it has an assigned attribute. If not, then the User attribute text stays the same.
okay so it remains a layer property and is not applied to the object.
Apparently this is already possible through scripting, but not exposed in the UI.
Iāll add this thread RH-60908 UserText: Expose Layer UserText in UI
I saw this thread too last night and it is very similar to what Iām asking for. But I want the the Attribute User Text to be applied to an object. What I mean by this is - say we load our custom Attribute User Text .csv. to Rhino and it will store it like a Standard/Setting. Then we can just select that from a dropdown list in the properties panel as opposed to loading it from a folder in our computer. Then, we apply it āBy Layerā which would bring up a check list of the existing layers in our rhino model that we can check (Like the way we apply materials by layer). Then all the Keys and Values would be applied to the objectās Attribute User Text.
But that is a different thing. Before you mentioned that changing the object layer will also change the attribute. That would mean the attribute on the object needs to stay aware that it was applied by layer, and be removed when that object changes layer.
If we would expose the layer attribute text. you could simply lookup the object, check on which layer it is, then check if that layer has an attribute and use that when you start processing your objects (e.g. in gh or script)
Let me try to explain my workflow better. I made a Ramp Creator grasshopper script that takes curves and uses their Attribute User Text as inputs for width, length, height, slope %. As you see below I have made 3 curves and I imported my custom Attributes.
The problem Iām focusing on is the lack of dynamism with the Rhino Attribute User Text. As Iāve explained in earlier posts, to assign these attributes I have to do - Select objects in Layer>Import Attributes>. I have to do this every time I create a new geometry. Now if we have a central attribute that we have the option to apply By Layer. Then I just have to create geometry on a layer and Iām off to the races. I know that every geometry I create from that layer will have those attributes. In the context of my grasshopper script I will only need to change the Values of the Attribute User Text. Now, I understand that there may be problems tracking the changes in attributes. Here is my proposal to fix those.
Dynamic Attributes - Attributes can be assigned in 2 states, āType Attributeā and āInstance Attributeā. Type Attribute means that the Keys and Values are assigned to every object on that layer and is by default āLockedā and āUniversalā (Meaning we canāt change the Values i.e. Width = 6 canāt be changed unless we āUnlock Itā). Instance Attribute on the other hand is an āUnlocked Type Attributeā. I would argue that the current Attribute User Text is already an Instance Attribute because itās Keys and Values exist on a per instance level(If I change the Key & Value of one object, it doesnāt affect the Key & Value of all the other objects).
This is what Iām proposing. Iām actually taking a lot from Revit. Its based on their Parameter System and is really useful in organizing data as well. I think this needs to be discussed more. Itās hard to explain myself in a few posts. Thanks.
Edit: I forgot to upload the file. Feel free to test out the Grasshopper script. Note that it requires Elefront 5 & Telepathy plugins to work.
