Commit 0450bcd1 added two extra fields to FontGlyph, texWidth_ and texHeight_,
but these weren't being initialized for bitmap fonts.
Bitmap text would sometimes randomly look OK if the uninitialized fields
contained large numbers, and fail if the fields contained zeroes.
Perform housekeeping at the last stage when all the build jobs in the build stage have completed.
Add a placeholder for new lint stage in primary CI.
Use alternate mirror branch to prevent technical error due to multiple commits being pushed to HEAD on slow moving build queues.
Close#1942.
[ci package]
Commit: dfe94e36ca
Message: Merge pull request #2014 from eugeneko/master
Prevent sending events for subscribers added during event handling.
The "resources being added into multiple groups" issue is not reproducible in Xcode IDE anymore, probably the more recent define_resources_dirs() macro has "properly" fixed it.
Subpixel-positioned text looks blurry, due to bilinear filtering of the
underlying texture. The basic idea here is to stretch the font glyphs
horizontally to increase the sharpness at subpixel positions. The
stretched images need to be smoothed to avoid aliasing artifacts; this
is done in FontFaceFreeType::BoxFilter().
Glyphs are always pixel-aligned vertically, so no vertical oversampling
is needed.
To make this feature comprehensible (I hope!) I've removed the
'subpixelGlyphPositions' flag and replaced it with a couple of values:
'fontSubpixelThreshold' sets the point at which subpixel positioning
kicks on, and 'fontOversampling' controls the amount of stretching.
The default values are 12pt text and 2x oversampling. These are fairly
conservative settings, which should improve small text without wasting
a lot of memory.
Note that when the font hint level is NORMAL (the default), subpixel
positioning and oversampling are both disabled. So, this feature doesn't
change any default behavior, and applies some hopefully sensible values
if the hint level is set to LIGHT or NONE.
Kerning values were being associated with the wrong char codes.
This was broken in commit 39930c9a, which moved some code around
to ensure that the space character is always the first one loaded.