search

MaxFour / Music-Player

Lightweight and Material designed Music Player
GNU General Public License v3.0
283 stars 71 forks source link

[Feature Request] Please fix this bad UI design. #49

Open Volker-Weissmann opened 5 years ago

Volker-Weissmann commented 5 years ago

I'm not sure if this is a bug or just bad UI design:

Let's say you are playing all your music in random order. If you tap on on song this song will be played and after this song the music-player will continue to play all music in random order. And it's perfectly fine that way. But if you search for a song using the search function and tap on it, this song will be played, but after this song the music-player won't continue to play all music in random order, instead, only this song will be in the queue. I don't think that it should be that way: It makes no sense, that tapping on a song result in a different behavior than searching for the name and tapping on it.

gkeegan commented 5 years ago

The current behaviour makes more sense to me tho. Tapping a song (without searching) is more for playlist use (ie starting the playlist with the tapped song as the first in the queue).

Searching for the name is the type of scenario where you want to listen to that one song and not have random songs play after (ie playing Christmas music for the family and not wanting rap with profanity to play after).

stendarr commented 4 years ago

This is all intended behaviour as far as I can tell. When the search results are displayed after searching for a song you can click on the three dots at the far right side of the song - this will give you the option to queue the song, either as the next song in the current playlist or as the last song in the current playlist.

It's possible however that this option didn't exist when you opened the issue. Either way, I think this issue can be closed.