Releases: tinne26/etxt
v0.0.8
Release for a minor fix:
Renderer.SelectionRect("\n")
was returning a height corresponding to two lines instead of one. In general, anystring
passed to the function that was made exclusively of\n
line breaks would report a height one line taller than expected.
This is an edge case, and it's still possible to be confused about what strings like "\n \n "
should return, when only spaces and line breaks are mixed up, so... I don't know. Even I'm not fully confident about what should happen in some of these cases, but I think the new behavior sticks closer to common sense than the old one.
The affectation is fairly limited and niche, but new users are encouraged to use the latest versions of both etxt and Ebitengine.
v0.0.7
Adding auto-detection and parsing of gzipped fonts on ParseFontBytes()
, partially motivated by the need in tinne26/fonts. Due to .ttf
and .otf
headers not colliding with gzip stream headers, this change doesn't break compatibility.
The oldest safe etxt version to use is still v0.0.4.
v0.0.6
With the release of Ebitengine 2.4.0, it's now possible to preserve image bounds. With this, it's been possible to remove the previous GlyphMask
struct hack.
Summary of changes:
- etxt v0.0.6 requires Ebitengine v2.4.1 (as v2.4.0 had an important bug on Windows).
- The
GlyphMask
struct hack for Ebitengine has finally been removed. - We are now using
embed.FS
instead of*embed.FS
(thanks Sedyh for reporting this one). RectSize
deprecatedWidthCeil()
andHeightCeil()
methods have now been fully removed.RectSize.Width.Ceil()
andRectSize.Height.Ceil()
are now directly suggested in the documentation instead.
Notice that despite the multiple breaking changes, it's ok to not update to v0.0.6 yet if you are working with an older Ebitengine version. No bugs have been found or fixed since v0.0.4, so it's safe to keep using v0.0.4 or v0.0.5 if you wish (or at least, as safe as the new version).
v0.0.5
v0.0.4
v0.0.3
v0.0.2
Enough things have happened that deserve a new release:
- Ebiten was renamed to Ebitengine and all documentation changed a while ago.
- Switched from .gzip to the far more standard .gz extension for font compression functions. This is a breaking change.
- FontLibrary.ParseEmbedDirFonts was not working. I was inexcusably loading local files instead of the embedded files.
In the meantime, there has also been progress with additional rasterizers for fancy effects, like the OutlinerRasterizer. This is still a work in progress, though.