Rockbox mail archiveSubject: RE: Next song wps
RE: Next song wps
From: Mark Bright <mark_at_redbreva.co.uk>
Date: Tue, 1 Jun 2004 09:02:45 +0100
That would be good, as I really like the Next Song info, but can fixing the
"can't dynamically update scrolling WPS lines" bug be part of any changes...
It seems that all the useful lines need to scroll, so next track info is
only readable about 30% of the time...
On a secondary note, the WPS definitions are starting to become very
complex, scrolling, alternate lines with next track info using conditional
checking.. Etc. would it be worth "Fine tuning" one with all the bits in
place and including it in the WPS documentation as an example?
|[mailto:rockbox-bounces_at_cool.haxx.se] On Behalf Of Hardeep Sidhu
|Sent: 01 June 2004 08:56
|To: Rockbox development
|Subject: Re: Next song wps
|Daniel Stenberg wrote:
|> On Mon, 31 May 2004, Hardeep Sidhu wrote:
|>> > The next song info is only available when the next song has
|>> > actually
|>> > (partially) been loaded into memory by Rockbox. Rockbox
|>> > the next song into memory when the current one is running out.
|>> We could always cache the next track path, making it available for
|>> the WPS at any time.
|> Yes, we could. But that would only allow the 'D' tags, not
|the 'F' and 'I'
|> ones that are dependent on the data in the mp3data struct in
|Why don't we cache the id3 info as well? We can load it at
|the same time we load the current track in the mpeg code,
|making the expense fairly minimal.
Received on 2004-06-01