4 ms·
Thanks for the answers! > Pathfinder's API is based around the concept of an atlas in order to improve batching. And the result of a raster job is then coordi
by jwilm 10y ago
Thanks for the answers!
> Pathfinder's API is based around the concept of an atlas in order to improve batching.
And the result of a raster job is then coordinates in the Atlas?
> Especially at small sizes it's a lot more efficient to render multiple glyphs all in one go without issuing separate draw calls for each one.
Makes sense
> There's nothing preventing you from making a separate "atlas" for each glyph if you want, though you'll pay some performance cost for this.
It's not exactly an atlas then is it :P. Sorry if I wasn't clear; I was trying to understand whether the library or the application is managing the Atlas. Sounds like the library.
- pcwalton 10y ago> And the result of a raster job is then coordinates in the Atlas? Yes. > Sorry if I wasn't clear; I was trying to understand whether the library or the application is managing the Atlas. Sounds like the library. The library manages the atlas, because it uses a particular packing algorithm that maximizes the performance of the accumulation step (by increasing parallelism) when rasterizing many glyphs at once.