Bug 180477 - queuing tracks on a filtered list does not queue the chosen tracks
Summary: queuing tracks on a filtered list does not queue the chosen tracks
Status: RESOLVED FIXED
Alias: None
Product: amarok
Classification: Applications
Component: Playlist (show other bugs)
Version: 2.0.1
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
: 185712 188711 190842 191306 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-01-12 17:36 UTC by Jason Martin
Modified: 2009-12-09 11:28 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Martin 2009-01-12 17:36:57 UTC
Version:           2.0.1 (using KDE 4.1.3)
OS:                Linux
Installed from:    Ubuntu Packages

If you filter the track list, then queue tracks in the filtered list, the queued tracks aren't the ones chosen. Also, the queued number does not appear in the filtered list. Once the filter is removed, the queued tracks show up on the playlist.
Comment 1 Greyor 2009-01-28 00:45:42 UTC
I've also had this problem on 2.0.1.1, and I just noticed it now. When you filter the tracks in a playlist and queue something, it queues the file at that position in the normal playlist -- I went back to the normal view and found a track queued at about the same place in the unfiltered list.

It's not a show-stopper, but it's mildly annoying.
Comment 2 Rindert Vonk 2009-01-29 19:25:16 UTC
The same issue does also occur when removing tracks from a filtered playlist. So it could be as wel be on all other action on filtered lists
Comment 3 Tim Boundy 2009-01-31 11:57:37 UTC
I get the same issue and consider it a show stopper. I have a collection of around 3000 songs and trying to queue up a song I want is impossible using the filter search, and very difficult to find using the standard "search as you type into the playlist" as the space character escapes the search criteria (but that's another issue).

Using Amarok 2.0.1.1 on KDE 4.2 (Arch Linux).
Comment 4 Seb Ruiz 2009-02-08 07:31:10 UTC
Confirmed.
Comment 5 Nikolaj Hald Nielsen 2009-02-14 16:15:50 UTC
SVN commit 925964 by nhnielsen:

Make queuing on a filtered playlist work as expected. The only issue now is that it is possible to have queued tracks that are not visible with the current filter. These will be played in order but no track will be marked as 
playing in the playlist. I am not sure this is something that is worth changing though as it is hard to sy what the "correct" behaviour in this case is (should a filter override a the order of the queue?).
BUG: 180477


 M  +5 -4      PlaylistActions.cpp  
 M  +10 -0     navigators/NavigatorFilterProxyModel.cpp  
 M  +3 -0      navigators/NavigatorFilterProxyModel.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=925964
Comment 6 Nikolaj Hald Nielsen 2009-02-27 15:28:27 UTC
*** Bug 185712 has been marked as a duplicate of this bug. ***
Comment 7 Jason Martin 2009-02-27 15:36:33 UTC
Would it be possible to have any queued tracked appear in order of queuing above the filtered list? My preference is to play the queued song no matter what the filter is now. The user queued it for a reason, right? :)

Maybe an example of how I use amarok would help. I have my complete collection, and from there I load up the playlist with songs or albums and have it on constant random play. If there's a specific song or songs that I want to listen to, I use the filter to find the song(s), queue them, then remove the filter. I don't leave the filter on for amarok to play in often, just as a search tool.
Comment 8 Nikolaj Hald Nielsen 2009-02-27 15:39:12 UTC
Queued track will be played in order, no matter if they are shown by the current filter or not (meaning that the queue might actually start playing a track that you cannot currently see.). Also, the queue is not reset when removing a filter. So as far as I can see, your use case should be ok.
Comment 9 Seb Ruiz 2009-04-03 07:00:32 UTC
*** Bug 188711 has been marked as a duplicate of this bug. ***
Comment 10 Dan Meltzer 2009-04-27 17:36:50 UTC
*** Bug 190842 has been marked as a duplicate of this bug. ***
Comment 11 Seb Ruiz 2009-05-03 06:12:41 UTC
*** Bug 191306 has been marked as a duplicate of this bug. ***