In ClipperLib, I used to use Orientation to determine winding order of output as part of a keyholing system to connect holes to outer perimeters. This method seems to not be available in ClipperLib2 and I wondered if this was planned.
As an additional note here, I would like to be able to force orientation, not just query it. I have a few cases where I'm not actually sure what my orientation is for the clipping geometry and used an explicit Positive for subject and Negative for clip in ClipperLib1. With the single fill rule now, I would like to be able to ensure the correct behavior
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes. I guess a combination of query and reverse would allow me to make a consistent sequence for a mix of differing Path orientations within Paths, with a convenient method to encapsulate this into a convenience call.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In ClipperLib, I used to use Orientation to determine winding order of output as part of a keyholing system to connect holes to outer perimeters. This method seems to not be available in ClipperLib2 and I wondered if this was planned.
I'll put this on my growing **todo ** list 😱.
I was futzing around with the C# code in my Github over here. Not sure if useful, but you'll see what I was tinkering with and missing:
https://github.com/philstopford/DesignLibs_GPL/tree/ClipperLib2/Common/clipper
As an additional note here, I would like to be able to force orientation, not just query it. I have a few cases where I'm not actually sure what my orientation is for the clipping geometry and used an explicit Positive for subject and Negative for clip in ClipperLib1. With the single fill rule now, I would like to be able to ensure the correct behavior
There is a
ReversePathsfunction but I suspect it hasn't been exposed as public.Yes. I guess a combination of query and reverse would allow me to make a consistent sequence for a mix of differing Path orientations within Paths, with a convenient method to encapsulate this into a convenience call.