Bug 14244 – Style on current track in current playlist is wrong when doing CM

Bug 14244 - Style on current track in current playlist is wrong when doing CM

Summary:

Style on current track in current playlist is wrong when doing CM

Status:	CLOSED FIXED

Product:	SqueezePlay
Classification:	Unclassified
Component:	UI
Version:	7.4.x
Platform:	PC Other

Importance:	P1 normal (vote)
Target Milestone:	7.4.0
Assigned To:	Wadzinski Tom

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-09-24 07:55 UTC by Wadzinski Tom
Modified:	2009-10-05 14:32 UTC (History)
CC List:	1 user (show)

See Also:
Category:	---

Attachments
Patch to fix albumcurrent styling for pressed and locked states (826 bytes, patch) 2009-09-24 08:10 UTC, Ben Klaas	Details \| Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Wadzinski Tom 2009-09-24 07:55:59 UTC

Comment 1 Ben Klaas 2009-09-24 08:10:22 UTC

Created attachment 5913 [details]
Patch to fix albumcurrent styling for pressed and locked states

Yer welcome :)

Comment 2 Ben Klaas 2009-09-24 08:10:59 UTC

FYI, this has been tested, is no risk, and fixes a broken UI in this spot.

Comment 3 SVN Bot 2009-09-24 10:13:46 UTC

 == Auto-comment from SVN commit #7745 to the jive repo by tom ==
 == https://svn.slimdevices.com/jive?view=revision&revision=7745 ==

Fixed Bug: 14244
Description:
- current item now correctly shown...

Comment 4 James Richardson 2009-10-05 14:32:33 UTC

This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server!
    * SqueezeCenter: 28672
    * Squeezebox 2 and 3: 130
    * Transporter: 80
    * Receiver: 65
    * Boom: 50
    * Controller: 7790
    * Radio: 7790  

Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes

If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html

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