is passable give different distance in list of point to delete
ex: point 1 - 30
point 2 - 20
point 3 - 10
...........
the point all in one list
i try a lot but didn't found the way ...
w list should contain a smallest value of the values with the same index. I should keep order of the indexes.
For example, item [21] of the 1st branch = 1, item [21] of the 2nd branch = 2, so item [21] in the resulting list = 1.
Any advise?…
ld go
Slider at 1 -> 1°, 2°, 3°.
Slider at 2 -> 2°, 4°, 6°
Slider at 3, etc.
And when the angle was too much that it surpassed 90 before connecting the 20 points, that line was not created. Maybe using a series instead of a range...mmm
Everything helps, thanks
…
s… (Numbers would be changing)
{0;0},{0;5},{0;13},{0;?}…,{{1;0},{1;3},{1;4},{1;21}…
What I currently have are a list of branches much like the ones above and a number of branch item lengths from pre-merged branches. With these lengths I have tried both using this data with the original path numbers to compare branches and decomposing the list of paths I want to cull into numbers to check though as the screen capture shows neither work as required.
Any ideas greatly appreciated.
Thank
Matt
…
cture, Rhino treats them as a single flat list. For example a surface can have 10 rows and 6 columns of control-points, resulting in a list of 60 points.
But 10 times 6 isn't the only way to get to 60. If you want to make a surface out of a list of 60 points, you'll also have to tell Rhino how those 60 points should be interpreted in terms of a grid. It could be 2*30, 3*20, 4*15, 5*12, 6*10, and all of the aforementioned products the other way around.
Sometimes there's only one way for a number of points to fit into a rectangular grid. For example if you provide 49 points, then 7*7 is the only way to make it work, but these cases are rare so we always demand you give us all the information required to actually make a rectangular grid of control-points from a linear collection.
As for "Why is it, sometimes we need to attach additional value into it?", this is usually because when you divide a domain or a curve into N segments, you end up with N+1 points. For example take the domain {0 to 5}, and divide it into 5 equal subdomains. You end up with {0 to 1}, {1 to 2}, {2 to 3}, {3 to 4} and {4 to 5}. However there are six numbers that mark the transitions between these domains 0, 1, 2, 3, 4 and 5. This is why you often have to add 1 to the UCount, because the number that controls the UCount often results in N+1 actual points.…
Added by David Rutten at 8:30am on December 25, 2014