Assigning different types of handle to doors and windows

[Leo13 (Leo)]

Hi,

I am doing some GH door and windows scripts and would like to know how to assign a list of handles ex: 4 types so I can choose/change the handle after putting the door to its host.

The handles can be internalized blocks from rhinoceros?

[arcus (Thomas Hardy)]

I was just working on a similar thing a few days ago. If you reference the block as a Text in grasshopper (you have to type in the name of the block) you can pull in different kinds of hardware.

Block Definition input in GH Styles

Following up on this thread again. Yes it would be really helpful if the block objects are somehow able to maintain their material assignments through grasshopper. I can get grasshopper to recognize the material as a ‘model brep’, but once it goes to ‘geo’ or normal ‘brep’ it loses the materials and it’s difficult to add them back. [image] For instance, this door panel has a glass lite in the middle, metal on the exterior, and wood on the interior. It’s possible to split each of these pieces…

[fsalla (Francesc Salla)]

@Leo13 you can also reference geometry from Rhino in Grasshopper (multiple Breps, for example), and connect it to a Data component. VisualARQ doesn’t support lists from the Brep component, but it does it for the “Data” component instead. This way, you can select the “internalise data” option in that Data component, so all objects are stored in that component. Once the geometry is internalised inside the Data component, you can disconnect it from the Brep component. You can do this with different Data components so they store different “handles”.

[Leo13 (Leo)]

If instead of being a brep it would be better if it is already a block? So I could take advantage of insert point?

Also, if I want to be able to choose between different handle bases, like squared round, and so on.. how could it be done?

I came across this situation and I don’t understand why it doesn’t work.

[fsalla (Francesc Salla)]

Hi @Leo13,

@Leo13

If instead of being a brep it would be better if it is already a block? So I could take advantage of insert point?

Using Block instances as input parameters for Grasshopper Styles might be not possible right now.
If you are using Rhino 8, you may have noticed that there are 2 “Block Instance” components.

One of them (the one like in your screenshot), is the VisualARQ one, inherited from VisualARQ 2 for Rhino 7 (VisualARQ 3 has kept it in order to be used in Rhino 7). This one can’t “internalise data” across documents.
The other “Block Instance” component, native in Rhino 8, can “internalise” data, but it’s not compatible with the VisualARQ Grasshopper Styles.
So for Grasshopper Styles, you can use “Block definitions” instead, and reference them by Name in a Value list, for example (if you need to pick one option or another). But of course, you need that these block definitions already exist in the document where you will use the Grasshopper Style.

@Leo13

Also, if I want to be able to choose between different handle bases, like squared round, and so on.. how could it be done?

You can use a Value list and Stream filter to pick one option or another, as I’ve shown in the previous post:

Just make sure the geometry you pick for each option, is located in the same reference point. Or depending on the geometry complexity of the handle, you can consider creating it directly in Grasshopper.

@Leo13

I came across this situation and I don’t understand why it doesn’t work.

There are 3 red components here:

1. Block instance: It gives you error because the “Block” input requires a Block definition, not a Block instance.
2. Block Decompose: Same as previous one. You need to plug there a Block definition.
3. Explode Blocks. I can’t find this component. Is it from a third-party Add-on? it might be not compatible with the VisualARQ Block Instance component.