Reordering in Queue Playlist causes that numbers in column "playing" disappear and so foobar forgets wich playlist and wich playlist entry the queued item belong.
Reordering in Queue Playlist causes that numbers in column "playing" disappear and so foobar forgets wich playlist and wich playlist entry the queued item belong.Edit:If that is by design to make the component work so i must say that this is the craziest component ever: it destroys origin functionality of the queue to force some features the queue wasn't designed for.
Is this the same Columns UI does with "View/Columns playlist/Activate now playing" command?
It would be possible to save queue between Foobars2000 sessions?
I believe that the queue is not saved by design (It's Not a Bug, It's a Feature! ). The queue itself was discussed in different (long and boring) topic, and AFAIR core developer(s) stated there that the queue should remain plain and simple. I think that is the reason you had to do 'tricks' in your code responsible for changing queue items' order - because the queue is not intended to support such operations.In other words, if you improve your component more and more, what will be the difference between using it, and using simple playlist with 'Remove After Playing' plugin (I remember that such thing existed somewhere)? You can already quickly send tracks to another playlist (eg. named 'Party' or 'Queue') using context-menu command.I don't want to sound discouraging here, as I believe that great number of users don't agree with core developers and were looking for component such as yours.Good luck
I am very aware that kerpondile surely put much effort in the development of this component. Also i am not interested to start a long and boring discussion about queues functionality.But:I hope i am allowed to mention that this component and all its praising is absurd. As mixcherry already said: All you can do with this component is possible without it - not in the sense of a workaround but in identical way if you use foo_utils. What is the long requested and needed functionality some people are talking about? Maybe you don't know foo_utils? Ok, now you know it! All the requests i read in this thread so far are realizable. Furthermore you don't have any restriction as you use a real playlist. You are not limited to 64 tracks and you also can choose playbackorder for your playlist. And if you like played track to be removed you can use foo_removeplayedHow far will the request concerning this new component go? mixcherry already bets that people will request to avoid flushback queue on starting another track manually. I bet that someone will request to start tracks inside of queue playlist manually or to avoid removal of played tracks. Such requests doesn't only mean ignorance of already existing funcionality but also confusion about the queue itself.This component would only makes sense if and only if it wouldn't show the queue in a playlist but in a panel outside of the playlist view. So the queue would be recognizeable as queue.
I agree it would be great if the queue would be a panel. Because I personally don't use the default UI, I'd prefer a Columns UI panel.Own panel would give users well-proven Winamp-like queue functionality - a feature foobar2000 should have had right from the start IMO.