Skip to content
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

ShapePath: Remove noHoles parameter. #24560

Merged
merged 1 commit into from
Aug 30, 2022
Merged

ShapePath: Remove noHoles parameter. #24560

merged 1 commit into from
Aug 30, 2022

Conversation

Mugen87
Copy link
Collaborator

@Mugen87 Mugen87 commented Aug 30, 2022

Related issue: -

Description

ShapePath.toShapes() has some limitations (#16950) and SVGLoader.createShapes() provides a better implementation. I think it makes sense to replace the implementation of ShapePath.toShapes() in future releases with the more robust code from SVGLoader.createShapes().

As a preparation, I suggest to remove the noHoles parameter from ShapePath.toShapes(). The contour/hole definitions should solely depend on the path definitions like in SVGLoader.createShapes() and not be configurable.

It seems the code base did not use the noHoles parameter anyway and I doubt it has a relevance in user level code.

@mrdoob mrdoob added this to the r144 milestone Aug 30, 2022
@mrdoob mrdoob merged commit bef5012 into mrdoob:dev Aug 30, 2022
@mrdoob
Copy link
Owner

mrdoob commented Aug 30, 2022

Thanks!

3jsLive pushed a commit to 3jsLive/three.js that referenced this pull request Aug 31, 2022
abernier pushed a commit to abernier/three.js that referenced this pull request Sep 16, 2022
abernier pushed a commit to abernier/three.js that referenced this pull request Sep 16, 2022
snagy pushed a commit to snagy/three.js-1 that referenced this pull request Sep 21, 2022
snagy pushed a commit to snagy/three.js-1 that referenced this pull request Sep 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants