Bug 140 - Playlist starts at top of list when pressing down to access next song
: Playlist starts at top of list when pressing down to access next song
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Player UI
: unspecified
: PC Windows XP
: P2 normal (vote)
: ---
Assigned To: Blackketter Dean
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-01-14 10:54 UTC by James Gardner
Modified: 2008-09-15 14:37 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James Gardner 2004-01-14 10:54:51 UTC
Playlist playing shuffled, pressed Down to see next track and found myself at
the top of the list, had to scroll all the way down past "Now Playing" to get to
the next track. I believe it was then ok.
Comment 1 KDF 2004-08-04 16:57:49 UTC
This seems to happen when teh payer is left sitting in "now playing" mode.  The
display keeps up with the current song, but the position in the playlist for the
scroll might be getting left at the song that it was at when entering "now
playing" mode.
Comment 2 KDF 2004-08-04 17:10:02 UTC
on second thought, this could be an illusion.  If the screensaver is set as "now
playing" it will display the currently playing song at all times.  pressing
'down' leaves the screensaver, going back to the former position in the playlist
before the screensaver engaged. The question is, what should the correct
behavious be?  It is jumping back modes, and storing the current position as it
should, but maybe  the screensaver should update 'browseplaylistindex' if it is
displayign 'now playing' with jumpback. 
Comment 3 KDF 2004-08-05 21:19:09 UTC
committed Aug 5, 2004
screensaver, when set to Now Playing (Jump Back on Wake) will stay in Now
Playing mode if already there.  This way, current song is maintained.
Comment 4 Chris Owens 2006-06-16 14:40:10 UTC
There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006.  I am setting them to targets of 6.2.1 to keep them from showing up in my queries.