C# NuGet issue with InflatePaths not present in .DLL (possible bug in NuGet)

[NicholasZiglioCaracol]

Edit: I just saw this: #593 I'm not sure if it is the same issue (if so, apologies for duplicating) or just a similar issue.

Hi @AngusJohnson, I have been using the clipper2 NuGet and noticed this strange issue when inflating (or should I say deflating as it is inwards?) far beyond the point where a Path64 becomes "inside-out".

I mean this with "inside-out" (not using clipper2 for this "deflation" but Rhino 3D + Grasshopper).

InsideOutPolyline.mp4

When using the clipper2 NuGet, the path gets smaller and then temporarily disappears when it becomes inside-out but on larger values some "inside-out" parts will return incorrectly with these kind of artifacts like so:

NuGetOffset.mp4

However when using the clipper2 .dll the path will get smaller, and then disappear never to be seen again (which is what I was expecting from the NuGet package):

dllOffset.mp4

I made a quick little project with the particular path64 saved as a .json where a colleague and I both reproduced the issue here: Clipper2NuGetIssue

Let me know if you need any more information.

PS. I wanted to thank you for all the work you have put in to clipper and clipper2. I have been using it for years and it is an amazing tool!

[olologin]

I believe this collapsing issue was recently fixed. Maybe nuget package is not yet updated.

[NicholasZiglioCaracol]

@olologin I think that is indeed the most probable explanation :) I'll stick to the latest dll for now and then try it again when the next NuGet is released.