Skip to content

Issues: hfutrell/BezierKit

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.

Sign up for GitHub

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

11 Open 9 Closed
11 Open 9 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

boundingBox vs boundingBoxOfPath follows opposite convention as CoreGraphics
#106 opened Dec 10, 2021 by hfutrell
Proposal: Use Sylvester Matrix for finding the intersection of cubic beziers
#99 opened Nov 3, 2021 by edudnyk
1
Impossible to make closed PathComponent
#97 opened Jul 14, 2021 by typoland
19
offset fatalError when all control points of segments are the same
#96 opened Jun 27, 2021 by typoland
3
Newton iteration may fail to converge, producing wrong results in curve.project()
#93 opened May 7, 2021 by hfutrell
droots can have low precision in some cases, which could affect Path.contains(_ point:) bug
#92 opened May 7, 2021 by hfutrell
@hfutrell
crossingsRemoved gets confused by coincident points
#84 opened Jan 21, 2021 by mbutterick
3
offset seems to treat straight & curved segments differently
#78 opened Dec 17, 2020 by mbutterick
3
Path.crossingRemoved() produces wrong result
#66 opened Aug 28, 2020 by ghenania
11
union with nonzero winding rule
#64 opened Aug 5, 2020 by mbutterick
9
Hard to work with ends of simple, unclosed bezier path
#20 opened Oct 14, 2018 by wolfmcnally
@hfutrell
2
ProTip! no:milestone will show everything without a milestone.