I saw a theme that had a nicer thicker font, so I went in there and took the fonts folder, and copied it over to the same locatoin ./720x720/font/ however I am not seeing it take effect after reboot even.
Is there something else needed? I looked at the instructions here: Custom Fonts | MustardOS and this seems to state they need to go in ./font/ folder instead. Which is correct? I am seeing no font changes. Thanks!
both are correct it will look at ./{resolution}/font first and then fall back to ./font
there is nothing else you have to do other than the bin file existing in your active directory.
naming matters.
default.bin = fall back if it does not find a {modulename}.bin file like muxplore.bin
also folder structure can matter depending on what font youâre trying to change
/720x720/font/panel/default.bin = font for list items
/720x720/font/header/default.bin = font for header items
/720x720/font/footer/default.bin = font for footer items
/720x720/font/default.bin = all other fonts. if any of the 3 above do not exist this is used.
Interesting. Itâs not working for me but I am doing exactly that as you described. Let me play with it more and see. It definitely works with the source theme I borrowed the font from. That one was on a different resolution folder is the only difference.
Well I have tried as instructed three times, in different ways/locations, and my font never changes. is there a global override perhaps in customizatoins? I couldnt find one but thatâs a thought. Actually with the other (âdonorâ) theme installed it does work, so that cant be itâŚ
EDIT: Im using the font from here: Release muOS Epic Noir Collection ¡ chronoss09/Theme-muOS-Goose ¡ GitHub
There is a setting for using them fonts vs language fonts but if it was set to language it wouldnât work when installing the other theme. Cannot say what youâre doing wrong but you could post the theme and what device youâre using
My apologies, I must have been VERY confused, because indeed the setting for font/language was the culprit. It works now.
Can someone clarify, what defines the font size on screen? Is it instrinsic to the font file itself, or can we resize the font by virtue of setting some of the CONTENT_ITEM_COUNT=XX plus padding parameters?
they are bitmap fonts so the size is set when you create the font. Itâs the -size parameter of this command
Thanks that is what I thought.
While on the topic, I find it odd that when installing my theme using my custom mytheme.muxthm it goes through an interesting few steps. First it installs the theme, and you see progress on terminal. Then it takes me back to the muos theme screen as one would expect. And when I back out of the theme screen it immediately opens a terminal window and installs something from my âalternateâ folder. My alternate folder has switchable font caps/lowercase (again, borrowed this from the epic noir theme linked above). I wonder if it is somehow triggering on its own?
Also, if I manually trigger the lower/upper case alternate âscriptsâ, they donât really do anything. Strange because my folder structure is kept near identical from the donor theme.
when including alternates you should also include an active.txt with what the default alternate is.
I donât know what âmanually trigger the lower/upper case alternate âscriptsââ means
Itâs just an alternate âoptionâ for the theme that installs a lowercase font in the right folder. I trigger it from the alternate options menu.
I figured out my issue. The XXXXX.muxalt file had 2 nested subfolders. Winzip loves to do that.