Open GoogleCodeExporter opened 9 years ago
Please, not even a simple comment regarding this from the devs, or am I the
only one using the Spotify-plugin on the server? Kind of a major bug not being
able to queue playlists or even start playing a playlist in Spotify. I can't
believe it's a _major_ hassle to implement?
Original comment by jer...@gmail.com
on 13 Dec 2014 at 12:17
I like to help you with this issue.
To do that I need some assistance. To start with please post the step you
perform to "Go to Spotify playlists", preferably accompanied by screenshots.
Also a screenshot of your server settings, plugins tab - showing the Spotify
plugin please.
Original comment by kaaho...@gmail.com
on 23 Dec 2014 at 11:20
Hello and thanks!
At Squeezer main menu / See numbered screenshots!
1 - Select "Internet Radio"
2 - Select "Spotify"
3 - Select "Playlists" (Here I think every playlist should have a submenu,
right?!)
4 - Select a spotify playlist.
5 - Now you have a list of songs in this playlist.
6 - For each song in the playlist, you have submenu for Play/Queue/Play Next
I think what is really missing, is the same little menu for each playlist,
that when pressed gives you options like Play/Queue/Play Next.
Like the menu you can get for each song in the playlist - See Screenshot 5 and
6 !
Thanks in advance! Keep up the good work! This app is what's keeping me happy
with
my Squeezebox!!
Ps. Maybe "Play", "Queue" and "Play Next" are easier/faster to read and
understand than
"Play", "Add to playlist" and "Play after the currently playing song"? Just a
thought....
Ds.
Original comment by jer...@gmail.com
on 25 Dec 2014 at 1:05
Attachments:
Thanks, I'll see what I can do
About the wording, "Play", "Queue" and "Play Next", my initial thinking, is
that you are right. I feel however, that the wording should be consistent
throughout the app, so if it's changed, it should be the same for all playable
items. I suggest you open a discussion on the group: Squeezer
<android-squeezer@googlegroups.com>, or create a separate issue.
Original comment by kaaho...@gmail.com
on 28 Dec 2014 at 6:39
Original issue reported on code.google.com by
jer...@gmail.com
on 8 Jan 2014 at 6:28Attachments: