(2013-12-30, 01:12)Tripp Wrote: Just curious if any progress has been made to enlarge the fonts yet? I had to move to another skin since my new furniture has me further away from the TV. I miss this skin so much!
I've done some work on it - its usable, but not anywhere close to being polished. There are some alignment issues and places where text scrolls or is cut off -- I'm not quite sure what I'm going to do about some of these areas yet, I might have to go with slightly smaller fonts or condense them a bit.
If you want to try what I've done so far I'd appreciate feedback on whether the font sizes are big enough (or even better, if they can go smaller) -- keep in mind that not all areas have been changed, but most views, plots, osd, home menu and info screen have bigger fonts. I'm not going to move onto the other less prominent areas until I can get those ones looking right first.
If you overwrite the contents of skin.arctic/1080i/Font.xml with this
http://pastebin.com/raw.php?i=xQgTNQZP
then restart xbmc, you should have an option for a "big" fontset in appearance options. I'd really appreciate some feedback on sizes.
(2013-12-30, 01:59)Nablamax Wrote: Tried that, home screen shows "loading" but doesn't show recent items or recommended/random items (everything activated in skin widgets). I'm on Frodo 12.3 and this used to work, can't remember when it stopped working.
I'm on 12.3 also, so its definitely working. On the panel home-screen the loading wheel displays when skin.widgets hasn't loaded yet, so my guess is its something wrong with the skin.widgets addon (rather than the skin). Does it work for other skins?
You could try manually deleting the service.skin.widgets folder from the addons folder and any of its saved packages in addons/packages/ (e.g. ~/.xbmc/addons/packages/service.skin.widgets-0.0.27.zip). Then restart xbmc and reinstall it. If you don't delete the packages when you uninstall or remove an addon, xbmc just uses the saved packages to reinstall it (rather than re-download) -- so if there was some problem with the package (e.g. a file was corrupted) then it will just cause the same problems because its using the same corrupted file. Its a long shot, but a possibility.