simplified in the bake name attribute and on the bake object component. I was counting on maintaining that structure.
{0;4}
{0;4}
{1;2}
{1;2}
Easily fixed with an additional attribute. Just curious on the behavior. Thanks.
…
Added by japhy to EleFront at 3:18pm on October 9, 2017
nts me this:
[[0], [0, 1], [0, 1, 2], [0, 1, 2, 3], [0, 1, 2, 3, 4], [0, 1, 2, 3, 4, 5], [0, 1, 2, 3, 4, 5, 6], [0, 1, 2, 3, 4, 5, 6, 7]]
this is what I wanted but how to convert this to tree in grasshopper?
In grasshopper I just get:
8x IronPython.Runtime.List…
branches in each A's list of B's, or remove its ends etcso that if I want to remove the last B in every A{0;1},{0;2},{0;3},{0;4},{0;5},{0;6}{1;1},{1;2},{1;3},{1;4}{2;1},{2;2},{2;3},{2;4},{2;5}would become{0;1},{0;2},{0;3},{0;4},{0;5}
{1;1},{1;2},{1;3}
{2;1},{2;2},{2;3},{2;4}I guess the question is do I need to figure out the cull pattern- each B may have different lengths...…
That is correct. In reality there are 3 major versions of .NET 1, 2, and 4 (different versions of mscorlib.dll)
Rhino 4 uses .NET 2 which includes 3 and 3.5.
Rhino 5 uses .NET 4