algorithmic modeling for Rhino
I have a tons of iterations that I am doing, and I am saving each solutions, everytime i do so, I have to save for example 30 out of 100 slider/inputs, I have to tick them manually everytime, this is extremely labour intensive, is there a way to create a favourite selections for the slider/inputs that I want to save in my save solutions?
Also, as I am saving different solutions with different name, would be awesome if I can rearrange them manually, currently there is no way I can rearrange them unless I recreate the whole solution save process with the right order, which is a nightmare already to think of it.
Can someone please shed some light?
If there are no apparent solutions, is there a way where i can save all the sliders/ inputs are one input so that I can just tick only one when im saving my solution?
Is there a way where I have a bunch of definitions in my GH to work as one definition? Something along that line? I'm trying to save time doing the labour intensive ticking and unticking during the save solution.
Tags:
For saving sliders, why you do not use panels instead of sliders?
As long as you have issues to have "bunch" of definitions, it seems that you are doing répétitive work.
So why dont you create a scripted component from the definition? You can make some clusters / user objects too. But having multiple files is also good option, otherwise creating grasshopper plugin helps to organise things too.
Thanks Petras
I think the inherit problem with clusters is that you cannot see the changes live whilst changing the parameters within (inside the cluster). Save solution works for only the cluster which is awesome, but it renders me pointless to use GH when I can't see what I am changing.. Its kinda like I'm giving up the live simulation for a Save Solution and vise versa.
Creating a plugin seems like a lot of work using VB script, correct me if I'm wrong?
Not if you are used to it. Visual studio templates for gh are ready made for typing just code to execute.
In the end if you have clear grasshopper definition that you using daily.
It is better to convert it to a script, + it will always be less code than in gh as it is pure rhinocommon.
At least I usually tend to write a component if I repeat the same procedure over and over, less wires, clear user interface.
Welcome to
Grasshopper
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
© 2024 Created by Scott Davidson. Powered by