Hi HPBEME. Should we pull that mod into the main Purity skin? It looks like you changed two files: Playerbar_Display and Tree_Background. Thanks.
Not really sure - obviously I don't work at J River, but I do appreciate your asking for my opinion. I was just trying to help a specific user out with that skin - it took me about ten times as long to write the explanatory post than it did to make the skin change! That said, the issue the OP was having would apply to anybody using the Purity skin with CloudPlay, so it probably does make sense to permanently incorporate those modifications.
You probably saw what I did with the PlayerBar display image, but I will describe the changes I made specifically, just to be sure: The images upper corners were nicely rounded, but the lower corners were almost sharp. I mirrored the upper half of the image to the lower half to make all the rounded corners symmetric, which to my eyes looks better.
I also increased the image height. Purity's default is to capture the
data only within its PlayerBar display "window", with the track slider and 3 lower right buttons (Repeat, Shuffle, DSP)
outside of it. As you know, in the main.XML file the user can change the Data Style from 0 to 1 in the <PlayerBar> section, which enlarges the display window to
include the track slider and three buttons within its borders. But the original image's short height resulted in no discernible difference when you toggled the Style setting. With the increased image height, you can now show the PlayerBar window two different ways as intended. I did not bother to explain all this in the original post… because… well… it would take so long to explain, hahahahaha.
We don't even know yet if the OP has tried out this modified skin and likes the change!
All that said, I really do think (as I noted in my 1st reply at the bottom) CloudPlay's content area should use the skin's XML specified list background color, and the CloudPlay header should use either the skin's specified tab Background or PlayList Header background color. That way you never have to worry about any color conflicts or poor contrast. Every skin uses text/background colors that are contrasting (some with better/higher contrast than others) - if they didn't, every skin's display would be problematic across all MC view types, not just CloudPlay.
I know that CloudPlay, Spotlight, and Streaming pages/views behave differently than all the other views, which I presume has something to do with those pages interfacing directly with the Internet (maybe?). So perhaps it's just not possible to point directly to a skins specified hex color, which is why CloudPlay's content background color is "sampled" from the tree background… is that correct? If however, that is not the case, then using approach I noted above would be much more robust and foolproof.