DEFECT: Default fanart image visible between artist fanart fades

[GoogleCodeExporter]

What steps will reproduce the problem?
**************************************

1. Load a playlist with more than one artist, where both artists have high
res fanart images.
2. Start playlist and switch to now playing window
3. FFWD to next track

What is the expected output? What do you see instead?
*****************************************************

Expect to see nice fade between each artist image.
Instead I can briefly see the default image

What sversion of the Fanart Handler plugin are you using?
*********************************************************

1.1 RC2

What skin and version of the skin are you using?
************************************************

StreamedMP 0.9.601
StreamedMP - SkinReleaseVersion-V1.5b for fanart plugin

Please provide any additional information below.
************************************************

I think this could be solved with the following method.
Default fanart background image is set to a black image.
Then a few secounds after no fanart is found then it fades in to the user
selected default background image.

Original issue reported on code.google.com by kiwijung...@gmail.com on 30 Jan 2010 at 2:05

[GoogleCodeExporter]

(or)

I think the current method/steps are;
1. Curent fanart fades out
2. Next fanart fades in

Instead could you do
1. Next fanart appears below current image
2. Current fanart fades out

Not sure if that would work as I don't pretend to understand how MP skin engine 
works.

Original comment by kiwijung...@gmail.com on 30 Jan 2010 at 2:31

[GoogleCodeExporter]

Hi,

I think this is because you don't use the visible tag correctly in the 
mymusicnowplaying.xml file. If you have the 
"<visible>!control.isvisible(91919294)</visible>" set on the default image then 
it 
should not be visible between image one and two.

Please verify.

best regards
cul8er

Original comment by markus_e...@telia.com on 1 Feb 2010 at 8:51

[GoogleCodeExporter]

I copied the code from your website's wiki over the code that trevor wrote, and 
it's
working properly now.  So yes it was a skinning error.  Sorry for the false 
report.

Original comment by kiwijung...@gmail.com on 1 Feb 2010 at 10:03

[GoogleCodeExporter]

Hi,

No problem and a BIG thank you for all your help testing this plugin. I really 
appreciate it.

best regards
cul8er

Original comment by markus_e...@telia.com on 1 Feb 2010 at 1:53

• Changed state: Invalid
• Added labels: Milestone-1.1
• Removed labels: Milestone-TobeDecided