Simple case:
I want to change the solid to some other pattern as well as scale and rotation.
What I am doing wrong here? Must be missing something obvious.
What I am doing wrong here? Must be missing something obvious.
Well. Getting inspired by your B input I moved hatch there and it works.
It was about changing the existing hatch, but I am happy with this solution, though I think it should work at H too.
1 Like
Yes I think that would help
Got another question: how to extract the colour from attributes?
In V7 it was dead obvious, in V8 it seems that I have to extract No3 from attributes and then deconstruct the text (?!). I must be wrong, it can’t be this bad.
I found another bug:
When the Model Hatch is linked directly it acts as supposed to, but when linked with Text it is loosing the properties.
and that makes no sense at all.
1 Like
I guess it sorta depends on what color you’re trying to retrieve. In the attributes list you show, there is Display Colour, Print Colour, and then there would also be Layer Colour. But, basically the key is to use the Model Object component. Remember, these components act as “Pass Through” components which means you can use them as a constructor and/or deconstructor.
So, let’s say you wanted to find the Display Colour attribute. You would first pass your hatch parameter into a Model Object component and then use a Display Attributes component to extract the attributes associated with the display. Something like this. Does that make sense?
You would find the Print Colour under the Drafting Attributes and Layer Colour under Layer Attributes.
2 Likes
Oddly I can not replicate this. When I pass a text panel directly into the pattern input, I get an error saying that it can not convert the Text into a Hatch Pattern. Can you upload your file (both Rhino and Grasshopper files) so I can see what’s happening here? What version of Rhino are you using?
Hi Andy
That make a lot of sense, only I was looking much closer.
V7 is more distinct in the properties search. You got drafting things, then solids then meshes and so on.
The Model Object name is slightly misleading (and the icon too) but I must admit it was my first approach to learn the new ribbon.
I am using the latest build. I have used the blank RH file with simple rectangular hatch. No need to send you this one.
mysz.gh (9.0 MB)
Well, generally speaking V7 didn’t really know much about actual object properties (unless you used a 3rd party plugin). So, it didn’t know about Layers, or Display Colour, etc. We’ve added all of those classes (natively) to V8 so all of these workflows are new. The word(s) “Model Object” basically just means that it’s an object that lives in the Rhino model… which means it contains many default attributes pertaining to Layers, Drafting Attributes, etc. Basically all of the properties that are exposed when you select an object in the Rhino model and open the Object Properties panel. A Model Object differs from just standard geometry parameters in Grasshopper which only contain information about the geometry, but do not retain any information about it’s attributes. I realize it’s not the easiest concept, but it was one we felt was needed in order to allow users access to all of the object properties that reside on objects within a Rhino model.
1 Like
Opening this file says it has missing 3rd party plugins (Human, etc.). Can you recreate a simplified example with only native components?
Sorry, wrong file attached.
hatch conversion.gh (17.9 KB)
I really love the opportunity it creates. I am looking forward to more test and discoveries.
1 Like
Andy
One more question. I couldn’t figure out on how to extract the hatch outlines. Is this possible?
We don’t really have an explicit method for extracting the hatch boundary but you could convert the hatch to a brep and then get the edges that way.
Oh! That would be a killer for my machine as I need to convert a 1500 complex meshes but I will give it a go.