Potential bug in recursive holes in polytrees #693
-
Hello I should preface this with the fact that I am using https://github.com/drlukeparry/pyclipr, rather than calling this directly However since it is fairly up to date and mostly seems to work I suspect this is likely a problem with clipper2 itself. Additionally this problem does not occur with clipper 1. I am using gdstk (which uses clipper1 under the hood) to generate visuals clpr.addPath(test_path, Subject, True) # closed path with subject type
PolyTree solution;
clpr.Exectue(Union, solution, EvenOdd); for reference the actual core python isn't much longer but the other functions I wrote to track this down are a bit longer pc = pyclipr.Clipper()
pc.addPath(test_shape, pyclipr.Subject)
out = pc.execute2(pyclipr.Union, pyclipr.EvenOdd)
pc.cleanUp() I found both cases where the 'seams' in the shape were horizontal to be broken to some degree. The labels in the upper left corner of each shape are their index in the tree where each number in the list is the index in the Children array from the polytree. The |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Using the latest Repository version ...
|
Beta Was this translation helpful? Give feedback.
Using the latest Repository version ...