thankssssss
.74-.80 may is ok not big differents .. but i have to control each group of triangles :)
___
sorry the version is
rhino 4.9
gr 0.8.0004 version
thanks :)
Added by architecture at 6:26am on December 20, 2011
ven if the number of panels inside each cell varies. The current solution works when the number of panels inside each cell is always two or other same numbers, but it wouldn't work if the number of panels inside frames are different in each cell. It would be perfect, if numbering of panels are automatically added correctly next to the cell number based on the number of panel division instead of feeding the fixed number.
To take an example, let's assume that the cell #80 has three panels and the #81 has two ones. In this case, three panels within the cell #80 would be numbered like 80-1, 80-2, 80-3, while two panels within the #81 would be numbered such as 81-1 and 81-2 automatically. …
ded a circle and been able to draw the two lines and cull out the correct distances but do not know how to pull out those two original lines - the one from the starting point to the circle division + the circle division to the end point.
To recap - I'm looking for a way to have 2 lines = 80" when the direct path between two points is 60". I do not want the 2 new lines to be equal in length but variable lengths.
thanks!
_patrick
…
. The rules to dispatch the lines are the next:
I start with a list that alternate true/false; like that: true, false, true, false.
If the angles between those lines are greater than 89° I want to inverse the next part of the list:
True, False, True, False, True, False,...
become
True, False, [>89°] False, True, False, True, [>89°] True, False,...
I managed to create a true false list, to check for the greater than 89° angle, to separate the lines relatively to the angles, but I don't know how to inverse part of the list at certain index.
(In the picture, I have written 90° but it should be 89°, I check for greater than 89° and not equal to 90° because in the real rhino model, the lines won't be exactly orthogonal)
If you have another idea to to reach the same result, it's also okay, I tried to find rules to solve the problems, but I may have overlooked other solutions !
And if there is some part of the patch that are correct but there is easier solution, I would love to learn as I am still new to grasshopper.
Thanks for taking the time to read. :)
…
tries, of different types, both annotation objects and curves, won't it be slow to iterate through all these objects for each rectangle?
I use 0.6.X but i'm soon making the shift to 0.7.X…
ve is most impacted by the characteristics of the vector field...If accuracy is not so important, you can use the curve re-sampling components to create a smoothe curve.…