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...