Replies: 4 comments
-
Your |
Beta Was this translation helpful? Give feedback.
-
Minkowski addition as I have read is always about the relation of sweeping one polygon along another polygon. I can understand how in the context of keeping the "inside polygon" this result is understandable, but I can't imagine much practical use. I'm after the points and something in Clipper is throwing away the lines and only keeping the polygons. My desire would be similar to the net result of Union, but because it should be swept Union will not always have the same result when the line is long or the polygon pattern is complex. How can I keep the outer boundary? For example where the black polygon is swept along the red line. Additionally when I add height Clipper gives an even more "incorrect" result as there are now angles on the polygon that shouldn't exist. It seems like Clipper needs further work when the path or pattern is open curve rather than polygon. Is there any trivial solution here?
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
The SVG looks better only because of the fill rule. Can you advise on the best approach to make this one polygon? Is it reasonable to loop the Paths64 MinkowskiSum() result values to create a new Path64 and then apply TrimCollinear()? Or can I use Clipper to Union the results from MinkowskiSum? You have the result in step 2 of my image above and I need to get to the final result of a single polygon. Please advise. |
Beta Was this translation helpful? Give feedback.
-
When using C# and editing sample project MinkowskiSum() uses a path that is an open curve where points become colinear the resulting curve is not the expected swept result and instead segments are missing. Please advise. See code snippet showing MinkowskiSum expected result, pattern curve, and actual result with missing segments.
Beta Was this translation helpful? Give feedback.
All reactions