Replies: 2 comments 5 replies
-
Output: |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
In the latest commit, the C++ Polytree class has had a major rewrite, so I'm hoping this issue has now been fixed. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi
I am using the float point version of the boolean code in Clipper2 and would like to confirm something.
I am using the C++ version of code.
basically, when I prepare the PathsD objects, I specify the polygon coordinates with float point, then use Execute() to get the boolean results (I used the PolyTreeD version of code, as the results may contain holes). However, when I tried to extract the boolean results, I find the coordiantes of the resultant polygons all scaled by 100. I think the code internally scale the input coordinates by 100 (or up to 8 decimal point), then perform the boolean using integer code.
this is fine, but I would suggest to scale the coordinates back when output. Otherwise I have to keep track the scaling factor. I did found the ClipperD's private member variable scale_, but can not figure out how to get this value.
Thanks
enuinc
Beta Was this translation helpful? Give feedback.
All reactions