This message was only really meant for themers (who I think have more
intelligence than brain dead monkeys), normal users will NEVER see
this issue.... the only possible way to have this come up is you load
keep loading .wps files in the browser (and they have many images)...
If you only ever load themes from the theme menu, or on startup then
you can go about your life not worrying about this... If you are a
themer and do come across this then simply load the attached .cfg file
(which is blank, no settings will be overwritten), it will reset the
skin buffer and you can go back to making sweet themes for us without
any graphical ability.

I will be adding stuff to make this more obvious shortly, but like I
said, this will almost never come up for regular users so its not a
high priority. (And I'm willing to bet that if I didnt sent that email
noone would ever have known anyway)

Jonathan

2009/8/16 Jonathan Gordon <jdgordy_at_gmail.com>:
> Hi all,
> I thing I forgot to mention in the commit message for r22350 is that
> you should load your .wps files from .cfg theme files (i.e not
> directly in the file browser), this is probably something you never do
> anyway, but I feel I need to let oyu know anyway...
> The new memory management stuff only resets the buffer when .cfg's are
> loaded, so if you manually load some image intensive .wps files
> directly it will eventually fail (silently) and you will get an empty
> now playing screen.. I'll add proper handling soon (it wont crash or
> anything so its still safe) and this is something that would almost
> never happen anyway so I'm not too worried..
>
> If this happens for you though, just load a .cfg theme file and it
> will start working again.
>
> Jonathan
>
-------------------------------------------------------------------
Unsubscribe: http://cool.haxx.se/cgi-bin/mailman/listinfo/rockbox
FAQ: http://www.rockbox.org/twiki/bin/view/Main/GeneralFAQ
Etiquette: http://www.rockbox.org/mail/etiquette.htmlReceived on 2009-08-16