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:50] john_e._finster |
how_to_create_custom_glcd_fonts_icons_bars_for_midibox_ng [2016/06/27 13:32] (current) psykhaze |
||
---|---|---|---|
Line 11: | Line 11: | ||
similar way. | similar way. | ||
- | Before I begin I´d like to point out some limitations: | + | Before I begin I´d like to point out some **limitations**: |
- | First, the height of fonts and icons is limited to a multiply of 8 (so 8, 16, 24,...pixels are possible). The | + | **First**, the height of fonts and icons is limited to a multiply of 8 (so 8, 16, 24,...pixels are possible). The |
width doesn´t seem to have limitations like this. | width doesn´t seem to have limitations like this. | ||
- | Second, the main goal here is to replace regular fonts with whatever graphics you´d like. In consequence, to | + | **Second**, the main goal here is to replace regular fonts with whatever graphics you´d like. In consequence, to |
use those graphics you have to point to a regular letter or a digit. So if you want to use a mute icon for | use those graphics you have to point to a regular letter or a digit. So if you want to use a mute icon for | ||
example and this mute icon sits on the spot where the regular "A" would sit, then the label of the element | example and this mute icon sits on the spot where the regular "A" would sit, then the label of the element | ||
Line 23: | Line 23: | ||
later. | later. | ||
- | Third, this tutorial only aplies to graphical lcds. | + | **Third**, implementing custom fonts in the way it is presented in this tutorial is not and can´t be made part of the official midibox repository. So every time the firmware gets updated and you want to keep your custom fonts, all the changes in step 3 of this tutorial has to be repeated.\\ |
+ | I can´t tell for sure, but I believe, if you update the repository the files changed by you don´t get updated. To assure that everything works after an update I recommend deleting all the changed files before the update and then getting all the new files again. | ||
+ | |||
+ | **Forth**, this tutorial only aplies to graphical lcds. | ||
Ok, let´s get to down to business | Ok, let´s get to down to business | ||
Line 263: | 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. | ||