This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
how_to_create_custom_glcd_fonts_icons_bars_for_midibox_ng [2014/05/11 11:58] john_e._finster [How to create custom GLCD fonts/icons/bars for Midibox NG] |
how_to_create_custom_glcd_fonts_icons_bars_for_midibox_ng [2016/06/27 13:32] (current) psykhaze |
||
---|---|---|---|
Line 266: | Line 266: | ||
As a solution I avoided painting the four corner pixels and left them white. | As a solution I avoided painting the four corner pixels and left them white. | ||
- | (Yes, I know! My examples here have painted corner pixels. They´re from a time when I wasn´t fully aware of that issue.) | + | (Yes, I know! My examples here have painted corner pixels 8-). They´re from a time when I wasn´t fully aware of that issue.) |
If you want to use only one GLCD, then this issue might not affect you at all. | If you want to use only one GLCD, then this issue might not affect you at all. | ||
+ | 2. Some special characters, which are already used by the midibox firmware to display certain elements (like "%" or "@") can cause the midibox to crash if they´re placed next to a font selector (like "&o@") or if they themselves are used as font selectors (like "&@"). I can´t totally explain why this is the case.\\ | ||
+ | I recommend avoiding the slots in the font file where those special characters normally would sit and also using them as a font selector | ||
+ | |||
+ | ==== Custom fonts database ==== | ||
+ | |||
+ | Here some fonts made by other can be downloaded. | ||