“should” and “GH2” are not part of my world. Those other things can be done before doing this.
I modified cClock to return ‘Plane Fit’ oriented for clockwise curve:
Which simplifies the ccVerts cluster:
InternalCross_2019Jul7f.gh (28.2 KB)
InternalCross_2019Jul7f.gh (28.2 KB)
3 Likes
Surface border component has its uses it seems, it’s new to me, but can see why you wanted it in the code would be good to have that as a GH2 native component.
As for the Simply Polyline, there a few native component options that go this such as :
Simplify Curve, Fit Curve. As if I remember right BullAnt is licensed not free unless you’re a student though it may have changed.
Relay is Native GH in Rhino V6, but not Rhino V5 so, for this reason, I personally try to keep replays to a minimum is if I think the code maybe need in V5. I understand your writing this code for yourself not others minds
1 Like
I probably use too many relays. I like to fit everything really close together and be able to see the data flow very clearly too.
If Simplify Curve works reliably on closed polylines, I’ll replace it in the cluster. I’ve had issues with it and with the rhino “merge all edges” command being totally reliable in some contexts, especially if the curves or edges from a solid that was created using a lot of booleans. Checking now, it looks like if I use double document tolerance for Simplify Curve with some badly drawn examples, everything works fine.
I use simplify polyline because I’ve never had it fail. same with the Topologizer plug in: very useful for correcting bad input that can break other components downstream. More things like that in GH2 would make me happy. Bridges between explicit and parametric are good.