-
-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not all subShapes returned from uniqueShapesCreatedFromSlicing for some Bezier paths #12
Comments
This is a strange one. It may take me a while to find the root cause, but in playing around with it I found that reversing the splitterPath with |
I think I have found what was wrong. In the splittingPath, there is a place where the end of |
Glad you found a way to get it to work. Can you post the splitter and splitting paths that don't work unless you make that 1 adjustment to the addLine call? and post the fixed splitting path too? that'll help me track down the problem when i have the test case for fail/succeed with that one small change. thanks! |
No change was made in splitterPath.debugDescription:
(before correction)
(after correction)
I hope this helps :) |
awesome :) many thanks for this test case |
Hi, I am trying to split the green part into 2 by considering the black box as the splitter path using
uniqueShapesCreatedFromSlicing
. It is working in most cases but there are some corner cases where it doesn't. Here,uniqueShapesCreatedFromSlicing
returns 1 value in the array instead of 2.Note: Consider the black box to be complete.
subShapes[0]!.fullPath().debugDescription:
splitterPath.debugDescription:
splittingPath.debugDescription:
The text was updated successfully, but these errors were encountered: