An unexpected situation occurred while using AddArc for testing

[inernoro]

I generated some unexpected results when using the following code
Sorry, his center point was accidentally relocated

 [InlineData(180, 360)]
 [InlineData(180, 359)]
 [InlineData(40, 359)]
 [InlineData(40, 360)]
 [InlineData(10, 359)]
 [InlineData(10, 360)]
 public Image<Rgba32> AddArcTest(int start, int sweep)
 {
     var r = 50;
     var image = new Image<Rgba32>(300, 300, Color.White);
     image.Mutate(x =>
     {
         var centerPoint = new Point(image.Width / 2, image.Height / 2);
         var yuan = new EllipsePolygon(centerPoint.X, centerPoint.Y, r, r);
         x.Draw(Color.Black, 1, yuan);

         var pathBuilder = new PathBuilder();
         var pointF = image.GetCenterPoint();
         pathBuilder.AddArc(pointF, r, r, 0, start, sweep);
         x.Draw(Color.Aqua, 2, pathBuilder.Build());
     });
     image.Save(AsVol($"{start}-{sweep}.png"));
     return image;
 }

40-360.png

40-359.png

180-360.png

10-359.png

10-360 .png

40-359.png

[JimBobSquarePants]

I've been having a dig through this, and the path builder is producing the correct output each time. There's something wrong with the polygon clipper.

Our clipper is a port of Clipper2 optimized for speed and memory usage and I've checked upstream with the original source and the issue is present there, so I've raised an issue.

[inernoro]

It seems that this is an exception rather than an issue with my usage. Has an issue been raised somewhere? I'll go take a look.

[JimBobSquarePants]

As I said, I’ve raised an issue with Clipper2. I’ll translate this into an issue so we can track the result there.

[inernoro]

I see it, but the issue you submitted appears to have been closed.

[JimBobSquarePants]

Yeah, because I was wrong...
I have a solution. I'll convert this now pending the PR.