In the code there's a reference to etOpenSingle as an EndType that isn't implemented in the library: "etOpenSingle: Offsets an open path in a single direction. Planned for a future update." I think this is what would do the trick if it were implemented. I would also love this functionality and I noticed Clipper v2 is in development, so I thought I'd bump this in case it could be considered for implementation. Angus, is this possible in Clipper v2, or something you would consider implementing, as...
Over the years I've occassionally used Clipper, which is great, and I can normally achieve desired results. However in this case, I'm struggling to get my head around the logic of what I want to achieve. I have some geometry (could be polylines or filled polygons) and I want to clip it to a large rectangle so outside of the rectangle is removed. That's relatively simple, but the tricky bit is that I also want the rectangle to join up any polylines to create filled areas, if that's possible. Hopefully...
Over the years I've occassionally used Clipper, which is great, and I can normally achieve desired results. However in this case, I'm struggling to get my head around the logic of what I want to achieve. I have some geometry (could be polylines or filled polygons) and I want to clip it to a large rectangle so outside of the rectangle is removed. That's relatively simple, but the tricky bit is that I also want the rectangle to join up any polylines to create filled areas, if that's possible. Hopefully...
Over the years I've occassionally used Clipper, which is great, and I can normally achieve desired results. However in this case, I'm struggling to get my head around the logic of what I want to achieve. I have some geometry (could be polylines or filled polygons) and I want to clip it to a large rectangle so outside of the rectangle is removed. That's relatively simple, but the tricky bit is that I also want the rectangle to join up any polylines to create filled areas, if that's possible. Hopefully...