Support and General Use > Theming and Appearance Customization

Volume bar on now playing screen with Classic theme on Sana clip+

<< < (3/3)

PDXmatt:
Originally I tried just adding %Fl(2,14-Terminus.fnt,64) #Track info font (fontId, filename,#glyphs) to the wps, but it did nothing. The same thing happened when I tried changing Classic's wps, I had to delete the # in front of the empty lines, but then the screen was messed up exactly like it is after changing PlusEsque's wps. Why is having spaces in between lines important?

Bilgus:
Anything following # is a comment and is a comment all the way till the end of the line if you are having issues you might try pressing return just prior to the command to push it to a new line.

Really thinking about it, it could also be that you are using windows to edit the file and the /r/n (thats carriage return newline) is messing with the theme engine since linux only uses /n to denote newlines (not sure).

You might try Notepad++ for windows https://notepad-plus-plus.org/

It will keep the newline convention of the file as you edit it you can also set the new-line convention for NEW files by going to Settings>Preferences>New Document>'UNIX LF'

Bilgus:
Here is PlusEsque.wps copied directly from my device with the edits you wanted to the font (works fine for my clip+)

--Edit sorry grabbed the wrong file

PDXmatt:
It worked, thank you for all your help! Maybe notepad is what was messing up my code. I already have notepad++, I'll try using that next time I edit wps files.

Navigation

[0] Message Index

[*] Previous page