Bug 4799 - Redundant display of track# in the Playlist screen of Handheld skin
: Redundant display of track# in the Playlist screen of Handheld skin
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Web Interface
: 6.5b2
: PC Windows XP
: P2 enhancement (vote)
: Future
Assigned To: Spies Steven
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-02 23:39 UTC by KB Lee
Modified: 2008-12-15 13:07 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments
Note the redundant display of track number, (26.25 KB, image/jpeg)
2007-03-02 23:41 UTC, KB Lee
Details

Note You need to log in before you can comment on or make changes to this bug.
Description KB Lee 2007-03-02 23:39:19 UTC
See enclosed illustration in JPG.
Comment 1 KB Lee 2007-03-02 23:41:22 UTC
Created attachment 1828 [details]
Note the redundant display of track number,

Note the redundant display of track number,
Comment 2 KDF 2007-03-03 17:38:51 UTC
If you try shuffling, I believe that you will find these are in fact playlist index, followed by track number. perhaps the  playlist index could be faded somewhat to make it a bit more distinct from the track number.  
Comment 3 Spies Steven 2007-03-05 11:07:16 UTC
Like KDF said the first number is the playlist position number. The second number is the track number. I am not sure why this skin shows the playlist position number so I am going to mark this as an enhancement. For now you can change how tracks are displayed in Slim Server by going to Server Settings and then Formatting and down to Title Format. From there you can choose or create a format that does not display the file's track number thus only displaying the playlist position number with this skin for instance. If you would like to keep the file's track number on this skin you could also add additional characters to differentiate the position number from the track number.
Comment 4 Michael Herger 2007-03-25 02:37:58 UTC
Change 11666 should align this skin's layout with the other skins.
Comment 5 James Richardson 2008-12-15 13:07:52 UTC
This bug appears to have been fixed in the latest release!

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.

Make sure to include the version number of the software you are seeing the error with.