Skip to content

gui_toolkit 0.17.1

Choose a tag to compare

View all tags
@sachahjkl sachahjkl released this 25 Oct 12:23
· 478 commits to master since this release
v0.17.1
This tag was signed with the committer’s verified signature.
sachahjkl Sacha
SSH Key Fingerprint: Jn721iAX7FFyZYdwo10ES1O41ssKkn7OJ9nHRT5Co2k
Verified
Learn about vigilant mode.
2ceb44a
This commit was signed with the committer’s verified signature.
sachahjkl Sacha
SSH Key Fingerprint: Jn721iAX7FFyZYdwo10ES1O41ssKkn7OJ9nHRT5Co2k
Verified
Learn about vigilant mode.

Fixed

  • Direct2D crash on nested PaintGlyph: Direct2D of Windows 11 24H2 as first released (d2d1.dll 10.0.26100.1, the image of GitHub's windows-2025 runners; a patched 24H2 such as 10.0.26100.8875 draws them) dies with a null read inside d2d1.dll, an access violation nothing can catch, when it draws a COLR v1 glyph whose paint graph has a PaintGlyph inside the paint of another PaintGlyph (a clip inside a clip, directly or through transforms, layers, compositions and PaintColrGlyph). With Color_Engine.System such glyphs are now drawn by the COLR interpreter (font.colr_nests_glyph finds them in the font's own tables, once per glyph and face); every other glyph still goes to Direct2D. font.colr_avoids_system(state, face, gid) tells which. Found by the CI of Wren: tests/colr interpreter_agrees_with_direct2d died on U+F1400 .. U+F140F of the test font, 16 glyphs, and the process with it.
  • tests/colr: the comparison with Direct2D leaves out the glyphs Direct2D is no longer given; nested_glyphs_stay_off_direct2d checks, without depending on the machine's d2d1.dll, that exactly those 16 glyphs are kept off it and are drawn in color by the interpreter.
Assets 2
Loading