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
strm2oas by default decomposes multi-point path with first or last segment length < halfwidth incorrectly.
They are read correctly as multi-point path by using the --lefdef-joined-paths option.
make bad; make xor shows the difference
make good; make xor doesn't
I mean, I don't know if the "good" version is even correct - that assumes a "GDS style" interpretation of path. Can you confirm the way these paths are build is compatible with other tools?
Like this "good" path:
while the "bad" version is correct if you imagine a square pen going round the corner left of the small segment:
It certainly looks like unintended, but I didn't just make it up.
I would say the fix is to warn about it and not break it into two point path.
The multipoint path is handled correctly after all.
I have an option to turn this into a polygon, because somebody got burned somewhere years ago by some tool not doing the right thing.
strm2oas by default decomposes multi-point path with first or last segment length < halfwidth incorrectly.
They are read correctly as multi-point path by using the --lefdef-joined-paths option.
make bad; make xor shows the difference
make good; make xor doesn't
test_spnet.tgz
The text was updated successfully, but these errors were encountered: