Font rendering inconsistencies with Component::setBufferedToImage() (iOS)

[amethystdeceiver]

@alexrdsp, thanks for stopping by! I don’t know about your context, but in my case g.getInternalContext().getPhysicalPixelScaleFactor() already returns 2.0f, so there would be no difference between the two.

As I mentioned, for me it was JUCE_DISABLE_COREGRAPHICS_FONT_SMOOTHING that did the trick of getting rid of both extra boldness and jaggedness.

I also implemented the repaint caching thing from this thread:

(SOLVED) Repaint() ignores opacity and repaints parent Component

After further testing: no, setBufferedToImage() isn’t good enough once there are components updated frequently enough by timer, so I went back to @pixelpacker’s caching thing and tweaked it a bit. Here’s the latest commit if anyone is interested. Works OK so far. (Note: I had to set JUCE_DISABLE_COREGRAPHICS_FONT_SMOOTHING=1 for the cached image to look the same as normal rendering.) Still I think an official solution would be beneficial for quite a lot of end-users - sometimes I can tell a…

which improved the responsiveness further. (There might be side-effects though, but I’ve yet to see them.)