This seems like a bug.
I’d think it’s more intuitive for the point index to match with the edge found.
file attached
indexwrong.gh (7.2 KB)
indexwrong Edtied V0.gh (14.9 KB)
I think it would be very nice if the outcome respects the order of the input points.
oh that’s what it’s for. i had no idea.
i wonder why the design decision to not just out put it in order, skipping the need for that “M” output.
was it a speed thing?
Hi @Will_Wang,
There are two lists to iterate through, so you’ve got to pick one.
Another complication is that the component can return more than one edge per point (the Valence parameter). So having a map as output makes sense.
If you want just one edge per point, then you can use something like the attached.
TestEdgesPt.gh (10.7 KB)
– Dale
1 Like