-
-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Unicode characters from any of the ranges on any display #256
Comments
davetcc
added a commit
that referenced
this issue
Nov 19, 2022
davetcc
added a commit
that referenced
this issue
Nov 21, 2022
davetcc
added a commit
that referenced
this issue
Nov 21, 2022
davetcc
added a commit
that referenced
this issue
Nov 21, 2022
davetcc
added a commit
that referenced
this issue
Nov 21, 2022
davetcc
pushed a commit
that referenced
this issue
Nov 23, 2022
davetcc
added a commit
that referenced
this issue
Nov 28, 2022
davetcc
added a commit
that referenced
this issue
Dec 1, 2022
davetcc
added a commit
that referenced
this issue
Dec 1, 2022
davetcc
added a commit
that referenced
this issue
Dec 3, 2022
davetcc
added a commit
that referenced
this issue
Dec 11, 2022
For 3.0, there are a couple of issues with font spacing for smaller displays such as OLED. These will be improved in 3.1. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Given that nearly all graphical displays are based on drawable, we can easily provide support for UTF8/Unicode on any display whatsoever by building it into tcMenu. This means that users can simply create their own font structure using the designer with just the right series of glyphs in it.
Designer will have a new screen under Code -> Font Creation Tool that will generate the header file, and these would then be usable with any display drawable. We already have most of the code on the embedded side, the most complex change is in desgner UI to allow graphical selection of the font glyphs to be included.
The text was updated successfully, but these errors were encountered: