3 ms·
Same, but the software could: 1. Optimize for rendering the on-screen fonts first, then fill in the rest after the user’s starting looking at them. 2. Cache t
by kstrauser 3y ago
Same, but the software could:
1. Optimize for rendering the on-screen fonts first, then fill in the rest after the user’s starting looking at them.
2. Cache the preview. If it takes longer to render the sample text than to load a png, save the rendering so you can load it again next time.
- dclowd9901 3y agoIt’s such a common idiom that fonts should have some kind of optimized “header” or something that can make it previewable but quick
- Clamchop 3y agoI think for this to be generally effective for Windows software, developers on the whole not being consistent or wanting to invest the effort in little bits of polish like that, they would need an API into a system-wide implementation. Which they could do, but it would take forever to see adoption in Windows culture, and Microsoft evidently cannot, just cannot, get their UI shit together.