This is a problem I'm having with most modern music players, in that it's messing with my cognitive model of what I expect to happen.

Here's the use case:
* In the music browser, open an arbitrary album
* Start playing from within the music browser
* Change the Artist/Album (making sure that the search results don't overlap with what was already there)

What will happen is that when that song ends, it will start playing from queue (or, the beginning of the currently displayed search results, if the queue is empty).

This is just alien to how I'm expecting things to work.  If I'm looking at Master of Puppets, and I start playing from that album within the library, even if I go to look at other albums I'm still operating under the impression that the player is playing Master of Puppets.  The last thing I told it to play was The Thing That Should Not Be.   I did not ask it to play whatever I happen to be searching for 

The queue is largley useless to me, as I can't have it repeat it's contents.  

The upshot of the current model is that the only way to put an album on repeat is either: 
 * create a new playlist for every album that I want to put on repeat, or have a scratch playlist that I have to clear and reload manually
 * leave that album in the browser as the search results and don't touch the application again

If the queue could be set to simply not empty itself out, even that would go a long way to making this usable.  As it is, it's incredibly frustrating.  

Is this something that could be implemented in an external extension -- something like Amarok's active playlist.  Is it possible to intercept the "start playing" event from the search results?