Releases: fiam/max7456tool
Releases · fiam/max7456tool
v0.7.3
v0.7.2: Stop rewriting pixels from 11 to 01 when decoding .mcm files
Rewriting was used for fixing the existing .mcm files in BF and INAV, which had invalid pixels that caused issues in some MAX7456 clones. These days, we support OSDs that can display 11 correctly as gray and support font metadata, so changing the values is problematic for those.
v0.7.1: Change shorthand for -verbose from -v to -V
-v clashes with the shorthand for printing the app version with urlfave/cli. This wasn't noticed in debug/ci because urlfave/cli only defines the --version/-v flag when the app version is non empty and we only fill it in for release builds. Thanks to @danarrib for the heads up.
v0.7: Add support for inheriting from a default font
Fonts that inherit from the default one don't need to duplicate their graphics anymore, instead we pull them from the default font. Also, if a duplicated character is found, a verbose message is printed to the console to let the user know they can safely delete the file. Eventually, this will be expanded to allow for more general inheritance.
v0.6
Add support for easily encoding colors in the metadata
v0.5.1
Add GH action for automatic releases
Version 0.5
- Added support for adding data to any character via auxiliary yaml files
Version 0.4
- Added support for specifying ranges in filenames
Version 0.3
- Added support for extended fonts (512 instead of 256 characters)
- Fixed a few metadata related bugs
Version 0.2
- Added support for encoding font metadata into
.mcm
files