Noticed this bug recently which is messing up some of my workflows. You can see it described below. The Rhino 5 + Grasshopper .9xx worked fine. Can we bring back the old join algo to have better expected outcomes?
See here in Rhino 5, take a triangle, explode it, and join it. You will see it kept the segment order and start/end point in the original place which is expected behavior. (You cannot see the red because the green exactly matches it.
RHINO 5 + GH.9xx
The same operation in Rhino 6 causes the edge order and start/end point to go wherever it wants after joining, which makes no sense to me. Is there a reason that was changed?
RHINO 6 + GH 1
I use this workflow often for things like fitting degree 2 arc segments of polycurves and then rejoining, as long as I don’t add new segments the segment and start/end point always stayed the same as the input curve which causes me to now have to do a different operation in R5 and R6 for the same task, R5 being the obvious intuitive way where R6 requires now some additional hacking to get the seam point back to where it belongs. Please bring back R5 + Gh.9xx join @stevebaer @DavidRutten
Here is the file for testing:
explode-join.gh (13.4 KB)