Rockbox mail archiveSubject: Multifont: testing & feedback
Multifont: testing & feedback
From: bk <mutualaid_at_gmail.com>
Date: Sat, 25 Feb 2006 21:10:31 -0500
My multifont patch is now basically functional. Preliminary patch is
Fonts are specified in theme .cfg files with the following tags:
browserfont, wpsfont, menufont, tunerfont, recordfont. The old font tag
is ignored if present.
Fonts selected through General Settings -> Display -> Browse Fonts
override the theme font settings, emulating the old behavior. This is
somewhat wasteful since we then have up to five copies of the same font
loaded into memory, but the total overhead is around 50k (worst case) so
I'm not too stressed about it. I debated implementing GUI menu items for
each font context but decided against it for the sake of simplicity.
- Plugins currently use FONT_PLUGIN which is def'd to FONT_SYSFIXED. I
don't know if it's worth implementing another setting for a plugin font.
That can be done easily enough if necessary.
- Some people may want separate font(s) for the remote display. One
additional font could be added for this, but I think adding five more
fonts (remote_wps_font, remote_menu_font, etc) is unwieldy and overkill.
- Font semantics are changed slightly. Code blocks are now responsible
for setting their appropriate font up front during initialization and
when refreshing . The old assumption seemed to be that whoever changed
the font needed to change it back to FONT_UI before returning. Now
there's no way to tell which context the function is returning to so
that won't work anymore.
- The recording screen is broken. I haven't done much work with it since
it isn't in the sim (any way to change this?).
Received on 2006-02-26