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
.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?
The text was updated successfully, but these errors were encountered:
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?
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.
.bounds()
only works for an individual BezierPath. In the fairly common case of creating aBezierPath.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?The text was updated successfully, but these errors were encountered: