Suggested Overloads

[rosspickard]

Hi Angus & Team,
Thanks for the updated clipper. I'm getting a better than 700% speed improvement in some operations. Here's a suggestion for overloading methods to make it even easier for us coders:
Add Path64/PathD support to the subject and clip for the Clipper UNION, INTERSECT and DIFFERENCE
e.g.
Clipper.Intersect( Path64 subject, Path64 clip, FillRule fillRule)
Clipper.Intersect( Paths64 subject, Path64 clip, FillRule fillRule)
Clipper.Intersect( Path64 subject, Paths64 clip, FillRule fillRule)

Yes, I know I can achieve the same through the Clipper64 class, but it just makes it a bit easier to include the overloads in the Clipper class too.

While I'm suggesting additions - how about a PolyPathToPaths64 function similar to the PolyTreeToPaths64?

[AngusJohnson]

HI Ross.
Thanks for the suggestion but I'm not persuaded that these overloads are warranted.
Re PolyPathToPaths64, I don't understand why you think this function (which is called recursively via PolyTreeToPaths64) should be exposed.

[rosspickard]

Hi Angus,
The reason behind the overload request is that I have a large number of instances where I am clipping a single Path64 shape by either another Path64 or Paths64. Having an overload would just cut down the coding. It's laziness on my part I know, so it's not a biggie.

For the PolyPathToPaths64 function I am often pulling out the individual child PolyPaths64 from a PolyTree64 operation and playing with them. Again not a biggie as I've created my own function to convert the Polytree back to the Paths64.

All the best Mate!