How to port SimplifyPolygon

[niki-sp]

void SimplifyPolygon(const Path &in_poly, Paths &out_polys, PolyFillType fillType)
{
  Clipper c;
  c.StrictlySimple(true);
  c.AddPath(in_poly, ptSubject, true);
  c.Execute(ctUnion, out_polys, fillType, fillType);
}

How to port this function as StrictlySimple() is missing from Clipper2 ?
Will just skipping StrictlySimple() produce intended result?

[AngusJohnson]

StrictlySimple never reliably rendered strictly simple solutions, and so it got the metaphorical chop.
At some point I do intend adding triangulation to the library but that is still quite a way off.
Alternatively, performing a union operation of clipping results will usually further simplfy results, but they won't normally be strictly simple.

[chrisdjali-wrld3d]

Do you have a ballpark estimate for when this situation might change? It would be useful to know if triangulation and splitting into simple polygons are things you've been working solidly on for the past few months since you answered the original question and might land any day now, or if they're still far-off nice-to-haves that might take a few years or never be implemented.

If it's looking more like the latter, if, as a domain expert, you've got any recommendations for a .NET library that can handle the splitting, that would be greatly appreciated. If you can't think of anything off the top of your head, that's fine, too, and I'll find/implement something myself.

[AngusJohnson]

Do you have a ballpark estimate for when this situation might change?

No, and sorry to disappoint. Just getting Clipper2 ver 1.0 finished took way longer than I expected, and now ver 1.1 keeps throwiing up new challenges too. Each time I think I've reached the summit, I find there's another one just above. But Clipper2 is getting much better 😁. And just for context regarding times, Clipper2 took numerous failed attempts over several years (partly due to health constraints) before I finally started making progress again.

or if they're still far-off nice-to-haves that might take a few years or never be implemented.

Yep. Treat it as vapourware at least until you see some solid code.

If it's looking more like the latter, if, as a domain expert, you've got any recommendations for a .NET library that can handle the splitting, that would be greatly appreciated. If you can't think of anything off the top of your head, that's fine, too, and I'll find/implement something myself.

Sorry. I don't have any recommendations.