Is there a grasshopper window/door method for using the same “Sizes” panel that’s available on the default windows/doors in VA3?
This would be amazing.
Hi @Clayton_Muhleman You can create a Value List parameter in Grasshopper with a list of sizes of your door and window. Would that work for you?
Hey Francesc,
That would work just fine.
Just from a user’s perspective, having two different interfaces/workflows for the user defined GH objects and for the VA native objects makes it potentially more confusing for other users in the office.
Thanks!
-Clay
Clayton, I understand that it might be confusing for the user to see two different window styles, and different features to edit them (because one is a system window, and the other a GH style one).
On the other hand, I wouldn’t show the same features of system windows as GH-style windows if they are different (like the sizes tab), which would add more confusion. Do you have any suggestions to make it more user-friendly?
For me it is a great advantage that we have a freedom with modelling such entities in quite different manners. And I usually use yet another windows styles, with external and linked blocks. It’s a matter of individual preferences, with a massive work on templates.
You can use a droplist for a pre-configured sized and other parameters, somewhere in the depths of this forum I showed the definition of beams modeled in this way.
Cheers, Jaro
My only thought was some sort of pre-cooked GH workflow that would allow us to point a GH input in the same direction as the sizes for the system windows. Like the “%<this.host.thickness>%” tag for setting depth.
No big deal, just seeing if this had been streamlined.
1 Like
The approach @Clayton_Muhleman suggests might also address the current problem with preserving the unique (per object) width/height of a GH window, while changing to the different GH style.
Currently, if I change my GH window to another GH window, it resets it’s dimensions to the GH style defaults. I must always double check the dimensions of each window and correct them after a style change.
I am referring to the modelling process, where each window is different in size, but driven with the same GH style. And as the design process goes on, I often need to iterate and change some of the windows to different GH styles.
1 Like
I agree. I think we could provide more options to link existing properties with parameters of VisualARQ Grasshopper styles, so if you change an object style, those common parameters will be preserved. Or recognize those parameters with the same name as the same parameter between objects of the same type.
2 Likes