, a1200)}) Is there any way I can make this list into {a1, a2, a3, a4, -a5, -a6, -a7, -a8, a9, a10, a11, a12, -a13, ..... , a1200} ? ( 4 positive signs then 4 negative signs and so on) - alternating every nth in general.
or
2. Is there any way (workaround) to get negative angle value from 2 vectors? I know 'ANGLE (of 2 vectors)' component by itself doesn't work and I know why too. I have feeling that the reflex angle output might be useful but again, matter of list manipulation.
Any help would be greatly appreciated. Thanks in advance.
Hyo
…
d' and no extension method 'AnnotativeScalingEnabled' accepting a first argument of type 'Rhino.Geometry.TextEntity' could be found (are you missing a using directive or an assembly reference?) (line 94)
Along with some warnings:
1. Warning (CS0618): 'Rhino.Geometry.AnnotationBase.Text' is obsolete: 'Use RichText or PlainText' (line 88)2. Warning (CS0618): 'Rhino.Geometry.AnnotationBase.FontIndex' is obsolete: 'Use Font property instead' (line 92)
3. Warning (CS0618): 'Rhino.RhinoDoc.Fonts' is obsolete: 'Use DimStyles table instead' (line 92)
I've downloaded the latest version of FabTools.
I've completely un-installed and re-installed.
I've Googled everything I can think of to find a solution, but most references are circa 2013 which is probably under Rhino 5. Which works totally fine, BTW.
Does anybody know of a solution?
Thanks,
Michael
…
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?…