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
Hi everyone,
InflatePaths doesn't check that its result stays in-range (it checks its input, though).
If slightly out-of-range, the result can look OK, but is not accepted as an input of a second InflatePaths because being out-of-range.
Going too far out-of-range results in an empty polygon.
In either case, no exception is raised.
Hi everyone,
InflatePaths doesn't check that its result stays in-range (it checks its input, though).
If slightly out-of-range, the result can look OK, but is not accepted as an input of a second InflatePaths because being out-of-range.
Going too far out-of-range results in an empty polygon.
In either case, no exception is raised.
The text was updated successfully, but these errors were encountered: