After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 620300 - Add option to not remove songs instantly from the queue after being played
Add option to not remove songs instantly from the queue after being played
Status: RESOLVED DUPLICATE of bug 582968
Product: rhythmbox
Classification: Other
Component: User Interface
0.12.x
Other Linux
: Normal enhancement
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-06-01 19:13 UTC by amano
Modified: 2010-06-01 22:34 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description amano 2010-06-01 19:13:00 UTC
That is the typical usecase:

I sit with my friends, drinking beer and listening to some songs that I queued up from my big library before.

After a cool song finished playing, my friend tells me that he liked the song and wants to know the band. I cannot remember and I cannot have a look, because the song has vanished from the play queue already.

Ideally the played songs should be greyed out and if I wanted to play them again, I should be able to move them to the songs in the queue that are to yet to be played.

Banshee implemented this feature with perhaps unneeded bonus features like autofill: http://versia.com/2009/09/23/updated-play-queue-in-banshee/ 

But keeping track of the songs played before is certainly a basic feature and should be added to rhythmbox as well. Maybe Zeitgeist can be used to keep track of those songs??

That would be a great feature to enhance the Rhythmbox experience (queueing up songs by middle clicking them like in Winamp would be another great feature).
Comment 1 Jonathan Matthew 2010-06-01 22:34:25 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 582968 ***