You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The below code outputs a path containing the coordinates [(4., 4.), (2., 4.), (2., 2.), (4., 2)]. Not sure if I'm overlooking something obvious, but if Clipper.addPath() assumes the added path is closed by default, shouldn't the output be [(4., 4.), (2., 4.), (2., 2.), (4., 2), (4., 4.)]? Or does pyclipr just assume a line segment between the first and last coordinates of a contour? I'm puzzled because Clipper's documentation ("Paths are closed when their ends do join (with an implicit line segment between the first and last vertices)") seems to imply the latter, while the example in the pyclipr readme uses paths whose first and last coordinates are the same. I'm using pyclipr 0.1.7 on MacOS 14.6.1.
The below code outputs a path containing the coordinates [(4., 4.), (2., 4.), (2., 2.), (4., 2)]. Not sure if I'm overlooking something obvious, but if Clipper.addPath() assumes the added path is closed by default, shouldn't the output be [(4., 4.), (2., 4.), (2., 2.), (4., 2), (4., 4.)]? Or does pyclipr just assume a line segment between the first and last coordinates of a contour? I'm puzzled because Clipper's documentation ("Paths are closed when their ends do join (with an implicit line segment between the first and last vertices)") seems to imply the latter, while the example in the pyclipr readme uses paths whose first and last coordinates are the same. I'm using pyclipr 0.1.7 on MacOS 14.6.1.
The text was updated successfully, but these errors were encountered: