I too find it backwards from what I expect. Sometimes (because of slight delays in the response) I click the button three or four times before I get the behaviour I'm wanting
.
I understand the logic of reflecting the current state, but to counter that logic: buttons should display what happens when you press them. The stop button shows a stop symbol not because the music is stopped, but because that's what happens when you press it. Same with the library button, same with the next track, previous track. Every other button in the interface displays what will happen when you press it.
Honestly it doesn't bother me overly much (it's not hard to get used to), but from a UX perspective, my feeling is that it should be switched. My two cents.
