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

BoundingBoxes of lists #16

Open
n8willis opened this issue Mar 17, 2021 · 2 comments
Open

BoundingBoxes of lists #16

n8willis opened this issue Mar 17, 2021 · 2 comments

Comments

@n8willis
Copy link

.bounds() only works for an individual BezierPath. In the fairly common case of creating a BezierPath.fromFonttoolsGlyph(), what you get back is actually a list of BezierPaths, so .bounds and its peers aren't directly usable.

Unless one of the asSomethingorother() representations actually solves this, and I'm not seeing it, that is?

@n8willis
Copy link
Author

I suppose a lot of the issues I'm opening lately really boil down to the fact that 'list of BezierPaths' a more common glyph topology than 'single BezierPath' is. So it seems like (IMO) there's enough to warrant the idea of representing that as a class. Have you explored that?

@simoncozens
Copy link
Owner

I haven't, because this wasn't specifically a glyph-based library (but was specifically a bezier-path-based library). But I do see a lot of opportunities for looking at things on a list-of-paths level. It always did feel a little off that fontFonttoolsGlyph created a list of paths when everything else created a path.

I think it's worthwhile. I don't know when I'll get around to it.

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

No branches or pull requests

2 participants