} (N=11) {0;1} (N=11) {0;2}(N = 11) {0;3}(N = 11) {0;4}(N = 11)
2. I run the Points that are coming out from the Divide Curve Components through the Path Mapper components with this definition:
{A;B} (i) > {A} (i)
3. I run data coming out from Path Mapper component through:
a) Parameter Viewer component and the result is:
{0} N=11 (data with 1 branches)
b) Point > Panel and the result is:
collection of 11 point (N=11) which is the exactly the same as the collection of point belonging to {0;4} (N = 11).
So, here is the question:
why the collection of points coming out from the Path Mapper {A;B} (i) > {A} (i) component is the same as the collection of points belonging to the curve {0;4}(N = 11) ?
Anyway ... It 's the first time I ask a question here... so I would like to thank you for what you do with your work! Thank you! You are really great!…
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…
dont get you, i am saying sleect numbers in range 1 to 10, starting from 1 with a step of 2.
1 to 10 by 3 = 1 4 7 10
1 to 10 by 5 = 1 6
1 to 10 by 1 = 1 to 10 = 1 2 3 4 5 6 7 8 9 10
Added by Steve Lewis at 3:15pm on November 11, 2013
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
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