Version 1.1 beta #354
Replies: 5 comments
-
I added printing the output on test failure even for Linux (and MacOS) builds, and it suggests that the problem is here: That still doesn't quite tell us what exact test that is coming from, but let me have a quick look into that. |
Beta Was this translation helpful? Give feedback.
-
|
Added some more output, which (when cleaned up just a bit) looks like this: I'll leave it to you to consider if the test criteria pertaining to those specific test numbers should just be relaxed a bit (similar to how many other tests are already treated here). In the meanwhile, I'm running my entire application-side test suite, on both Windows and Linux, against your v1.1 beta.` |
Beta Was this translation helpful? Give feedback.
-
|
And I've just spotted and fixed a bug but it's bedtime so I'll upload it in the morning. 💤 |
Beta Was this translation helpful? Give feedback.
-
|
I've just uploaded the promised bugfix (to address Issue #308). |
Beta Was this translation helpful? Give feedback.
-
|
At the risk of stating the obvious, these are the tests that are currently erroring out on MacOS: |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I've just now updated the Beta branch. And with these latest changes I think the code is pretty solid.
This beta (ver 1.1) contains a major rewrite of code that merges touching polygons in clipping solutions.
The old code was really ugly just as it was in Clipper1, and that incidentally was the main reason I embarked on Clipper2.
Anyhow finally with ver 1.1, this merging code is miuch simpler (while still not simple) and will be much easier to maintain.
And it does a better job of merging polygons too. (Note: I don't think this could ever be perfect without massively compromising performance.) WRT Performance, there's little or no difference between Clipper2 1.0 and ver 1.1.
So far I haven't had any feedback on this beta version. So now I'm asking users to try it out, and please let me know if you do (or don't) encounter issues/bugs. Thanks A.
ps: While C++ CI testing passes on Windows machines, it's currently failing in Linux. I'm pretty sure this is just an issue with a CI test and not a problem with the Clipper2 code. Unfortunately I don't currently have a Linux machine to locate exactly where (and why) it's failing.
Beta Was this translation helpful? Give feedback.
All reactions