algorithmic modeling for Rhino
Nice work man - just a finishing touch: could be nice with a description on the C parameter:
false- gimme a doggie bag
true- toss the leftovers
Dunno why the ceiling isn't working inside the series expression... what are you getting in there incorrectly rounded ints? unrounded Numbers?
cheers
indeed it is self-explanatory, but its nice to play with polishing the clusters to make them even more user friendly...
if you double click on a cluster input arrow - you can override the default name, nickname and description...
in this way you can get the one letter visible on the component, and on roll over get the name, type and description info.
note: the attached example isn't a full user object, just a cluster derived from Pieter's most recent definition with the C input description added.
very useful Pieter, thanks :)
i didn't test the new one with multiple lists yet, no... maybe tomorrow... you can always use the exploration i did earlier with multiple lists and swap in the new UO...
cheers
unfortunately, the answer is: it depends.
If the component is adding something to the tree that is relevant then it makes sense to add branches.
If it is just manipulating within a list or tree, then maybe not.
Ex: if i have 3 rectangles sent in at {0;0} and i make a component to return the 2nd edge and 4th edge of each of them, i need to have a new branch level so that i will have 2 edges in each of three new branches
{0;0;0}(N=2)
{0;0;1}(N=2)
{0;0;2}(N=2)
if i simplified back into {0;0} then i would have N=6 but the data wouldn't be divided as logically into meaningful sets.
(its getting late - i hope this makes sense)... good luck and good night...
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
Added by Parametric House 0 Comments 0 Likes
© 2024 Created by Scott Davidson. Powered by