algorithmic modeling for Rhino
When you window-select objects in Rhino, the order in which they are returned is by ascending runtime-serial-number. Whenever an object is added or changed in any way, it gets a new runtime serial number. So you cannot rely on a window-selection to give you what you want. Of course if you generate the points directly in Grasshopper, there is a logical order to them, even though it may not be the order you need.
If you want to import points in an ordered fashion from Rhino, you'll need to either select them in the right order, or sort them afterwards.
Thanks you very much for all the help guys. that is exactly what i needed :)
Hi again, sorry for being a bit anoying. although it was exactly what i needed, now i have given up trying to connect the point as it is imposible to create the line adequately, so i have then drawn them over the point as shown below.
i know how to go from surface to triangualtion, but i cant figure out how to go from the lines to exploded surfaces in between.
im really stuck with this and it is the source of my study, thanks
Is this any good? It uses the Compare component by @nzarchitecture from http://www.parametricmodel.com/Compareeveryiteminalist/38.html
It's a bit of a brute force method and doesn't make use of the 2D sorting algorithm discussed here. The basics are it creates a line between every point without duplication (Hence the Compare component) and then culls every line outside a set length domain.
hI, a fellow user redirected me to this thread, but i have not been able to apply the definitions to my problem,here is the post
Thank you so much in advance
Yeah it was me that sent you here. I was refering to the post for
This file shows the basic idea of 2D sorting. If you don't understand why it requires an expression like:
from + (along * 1000)
let me know, I'll try to explain.
There is a ghx attached to that post which will sort primarily on the X direction (along) and then any identical X will be diferentiated by the Y (from).
The top image was posted by me when asking the question "Is there a more elegant way?" The answer came back that % instead of \ was all that was needed.
The next two were posted by me as an answer to a specific problem, they do the same job. Which is to append a point as the first branch by giving the two trees the same data structure and moving the existing tree along a branch.
The third was posted by Beltrán Fernández Mariño in answer to the question about grouping items on branches.
And the last was quite possibly the first real insight for everyone into the inner workings of the Pathmapper. It was posted by Sameer Kumar, and if you do a google image search on "pathmapper" that's the first image to come up.
Thank you Danny for your post. I have to save the names next time. Authors sould be always honored!