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
Experimentation shows that they rely on being able to render multi-polygons with winding number in/out rules, which is beyond the capabilities of FrameBuffer. Might be able to fake it by testing the initial point of a contour to see if it is set.
Putting this on the back burner - this is effectively needing either a custom renderer or on-the-fly rendering into a bit buffer for every character write. Both are likely to be too slow.
Might be able to fake it by testing the initial point of a contour to see if it is set.
Could probably fake it by xor-ing subsequent curves, since fonts are not usually self-intersecting, but that means needing a temporary buffer to work with to get the mask, at least for multi-curve fonts.
The minified vector fonts from https://github.com/lowfatcode/alright-fonts may be better than bitmap fonts.
The text was updated successfully, but these errors were encountered: