Activity for DaveInCaz
-
DaveInCaz created ticket #2316
Entering the wrong password when extracting a ZIP results in a zero byte file
-
Incorrect SYSTEM_WGETRC is reported (Windows 10)
-
Diff Pane could show case differences even if they are ignored for actual diffing purposes
-
Got it, thanks.
-
Thank you, I did not see that FAQ entry. One workaround would be to do n-1 union operations in order to union n objects. But that seems simplistic. Instead, is a better approach to keep unioning the contents of the solution set until it diminishes to a single contour or at least reduces to an unchanging minimum number of (possibly non-overlapping) contours?
-
I did a simple example of unioning three adjacent rectangles. I was expecting a single polygon returned, but instead I got two. Starting point - 3 independent closed polygons: e.g., the orange and green paths are both adjacent to the yellow path. But the resulting union solution set still includes the orange path as an independent entity. Result of unioning those 3 polygons shown in black: If I perform a second union on the results of the first, then it does indeed produce a single polygon. A second...
-
I did a simple example of unioning three adjacent rectangles. I was expecting a single polygon returned, but instead I got two. Starting point - 3 independent polygons: e.g., the orange and green paths are both adjacent to the yellow path. But the resulting union solution set still includes the orange path as an independent entity. Result of unioning those 3 polygons shown in black: If I perform a second union on the results of the first, then it does indeed produce a single polygon. A second observation...
-
I did a simple example of unioning three adjacent rectangles. I was expecting a single polygon returned, but instead I got two. Starting point - 3 independent polygons: e.g., the orange and green paths are both adjacent to the yellow path. But the resulting union solution set still includes the orange path as an independent entity. Result of unioning those 3 polygons: If I perform a second union on the results of the first, then it does indeed produce a single polygon. A second observation is that...
-
I did a simple example of unioning three adjacent rectangles. I was expecting a single polygon returned, but instead I got two. Starting point - 3 independent polygons: e.g., path 1 and path 3 are both adjacent to path 2. But the resulting union solution set still includes path 1 as an independent entity. Result of unioning those 3 polygons: If I perform a second union on the results of the first, then it does indeed produce a single polygon. A second observation is that if I OMIT path 3, then indeed...
-
I did a simple example of unioning three adjacent rectangles. I was expecting a single polygon returned, but instead I got two. e.g., path 1 and path 3 are both adjacent to path 2. But the resulting union solution set still includes path 1 as an independent entity. If I perform a second union on the results of the first, then it does indeed produce a single polygon. A second observation is that if I OMIT path 3, then indeed the returned solution shows an actual union of paths 1 and 2. I don't really...
-
I did a simple example of unioning three adjacent rectangles. I was expecting a single polygon returned, but instead I got two. e.g., path 1 and path 3 are both adjacent to path 2. But the resulting union solution set still includes path 1 as an independent entity. If I perform a second union on the results of the first, then it does indeed produce a single polygon. A second observation is that if I OMIT path 3, then indeed the returned solution shows an actual union of paths 1 and 2. I don't really...
-
The following Nuget project appears to provide a compiled version of Clipper for dotnet: https://www.nuget.org/packages/Clipper/ However, the Nuget package isn't maintained by the same person as the Clipper source code (Angus Johnson), and its not clear whether it is really up to date or not. For instance, it is labelled 6.4.0 and yet if you install it into Visual Studio, instead it then looks like 6.2. Also it does not have a Clipper.AddPath() method but instead a Clipper.AddPolygon() method......
1
