Possible bug with remove from queue... If an item is in queue multiple times, removing one instance from queue (by selecting the item from the queue playlist, and using "remove from queue") removes all instances. Is this intended?

EDIT: Added the "by selecting item from queue playlist..." to clarify my question.

I suspect it probably is, how would foobar know which instance to remove?

Well, when i select a track and click "remove from queue", I would expect only the selected thing to be removed.

You meant other items than the one selected are also removed, or all of the selected item queued instances are removed? If it's the latter I think it's the way that command works, not a bug. I haven't experienced the first problem I mentioned though.

But if the item is in the queue multiple times which one is it supposed to remove? The first one? the last one?

Its like playing hangman, if someone guesses a letter you put the letter in in every place it occurs.

Well, the queue is indexed so by removing whichever file that is at the specified index should remove only that file even though the file may exist multiple times.

As it is now I guess it matches by name and not index.

That said, I'd guess it's working as intended though.

Oh wait. I wasn't being clear:

When I'm viewing the queue playlist, through foo_pqview, and I select an instance and ask it to be removed from queue, why are all instances removed?

I'll update the first post to be more clear.

Standard reply:
Queue functionality is already redundant to what you can do with playlists. While queue could be made much more complicated to suit everyone's needs, I believe that it would be a waste of effort as it would only mean duplicating functionality already present in playlists. If this issue offends you, you should seriously consider using a playlist instead of the queue.