g these times itself). If it works on selection alone, it would probably implement faster.
Theoretically, does this mean the total solving time of the definition is the 'chain of components' that takes the longest time? In the picture above, it would be the chain consisting 'point-curve-divideDistance'?
Because that still adds up only to 97%, I am assuming the Point and Slider component start solving in parallel, and the two Divide components also start solving in parallel?…
"surfaces" ? Our teacher said to place the truncation according to this relation : Capture%20d%E2%80%99%C3%A9cran%202016-05-01%20%C3%A0%2008.03.46.png I already make the five platonic polyhedrons in Rhino.
Best,
Nastia …
omponent that increases in the x-axis (example below).
A1 A2 A3 A4 A5 etc...B1 B2 B3 B4 B5 etc...C1 C2 C3 C4 C5 etc...D1 D2 D3 D4 D5 etc...
This is as far as I've gotten:
I have collected my points on the grid into a "List Length" component and input that into a "Series" which input into a "Function" with the expression Format("A{0}",x). The result labeling resembles the example below.
A1 A2 A3 A4 A5
A6 A7 A8 A9 A10
A11 A12 A13 A14 A15 etc...
Any help is appreciated.
Thank you in advance.…
I don't think I know what you mean. If it is that you want the curve numbers written out as text tags, use the reworked example below and adjust it to your needs.
/Ola
old version that has been fixed by now. I'd ask you to test this on the Rhino6 beta (which I am using to test this), but it looks like you're using a cracked version of Rhino so you probably don't have access to that.…