A suggestion for enqueuing/"play next" that won't break 2.x skins.

[gunslinger008]

As I understand it the major problem with implementing the much-requested enqueuing/"play next" feature is that marking which songs have been enqueued would require a change to the 2.x skin layout. However, I have a suggestion for marking the enqueued songs that I don't think would cause such a problem.

It seems like the playlist is just two columns of lines of text: one column for the line numbers + song titles and one for the song times. And since the line numbers are optional it seems like we can pre-pend text to each playlist line. So how about adding text markers to the beginning of enqueued songs' playlist entries?

For example, take the following section of a playlist...

75. Radiohead -{Hail to the Thief 06}- Where I End And You Begin
76. Radiohead -{Hail to the Thief 07}- Suck Young Blood
77. Radiohead -{Hail to the Thief 08}- The Gloaming
78. Radiohead -{Hail to the Thief 09}- There There
79. Radiohead -{Hail to the Thief 10}- I Will
80. Radiohead -{Hail to the Thief 11}- Punch Up At A Wedding
81. Radiohead -{Hail to the Thief 12}- Myxamatosis

Let's say song #80 is enqueued, then it might be marked like this:

75. Radiohead -{Hail to the Thief 06}- Where I End And You Begin
76. Radiohead -{Hail to the Thief 07}- Suck Young Blood
77. Radiohead -{Hail to the Thief 08}- The Gloaming
78. Radiohead -{Hail to the Thief 09}- There There
79. Radiohead -{Hail to the Thief 10}- I Will
((1)) 80. Radiohead -{Hail to the Thief 11}- Punch Up At A Wedding
81. Radiohead -{Hail to the Thief 12}- Myxamatosis

And if another song, say #77 is enqueued, then we'd have:

75. Radiohead -{Hail to the Thief 06}- Where I End And You Begin
76. Radiohead -{Hail to the Thief 07}- Suck Young Blood
((2)) 77. Radiohead -{Hail to the Thief 08}- The Gloaming
78. Radiohead -{Hail to the Thief 09}- There There
79. Radiohead -{Hail to the Thief 10}- I Will
((1)) 80. Radiohead -{Hail to the Thief 11}- Punch Up At A Wedding
81. Radiohead -{Hail to the Thief 12}- Myxamatosis

'((#))' might not be the best style to use, maybe something like '#>>' instead, but you get the idea.

Not exactly the most elegant approach, but it seems like this should work, and the enqueued songs would be marked pretty clearly due to the added mark + the indentation.

Sorry if this idea has been suggested before (and by that I mean the text marker approach; I know how often the general enqueuing feature is suggested/requested). With the amount of interest in seeing enqueuing in Winamp 2/5 this probably has been thought of before, but I thought I'd throw it out there just in case.

Cheers,
Sean

[amano]

jup. that shouldn't break anything.
you could select it with a right click
maybe even in the "Jump to file" dialog.


so for long playlists you can search the song in the "jumpp to file" dialog and right click it to be played next. then it would be marked as you proposed.

[Dipso]

yea, could work, lets hope this gets done!

[Mmusicman]

Amen!

[UltraZelda64]

I don't like the sound of "((1.))", and "#>>" doesn't look too good either, so... either leave it out if WA5 can't do it right, or find a better way to add this. It was useful in Winamp3, but not THAT useful.

[Mmusicman]

Originally posted by UltraZelda64
It was useful in Winamp3, but not THAT useful.

I totally disagree with you, and so do many others who constantly request the "que-next" option...perhaps one of the most requested wishes in the forums.

You may not need it, but I do! (currently using "Winque" to perform this function).

I'd like to see it as a right click option with the "J" function...or even more preferrably as a dbl-click option in that search window...

[UltraZelda64]

Yeah, I know, it was sometimes useful, but to me, overall it wasn't THAT useful. Of course, I'm not speaking for everyone. I might be one of only a few. If it can somehow make its way into WA5, then cool! But if not, it's nothing I'll lose sleep over. And if it's put into Winamp similar to what was mentioned... then, bleh...

[Plague]

I still propose that they redesign the pledit entirely, using the gen.bmp (and standardframe for modern skins) to skin it, instead of the normal pledit skin.
That way, they could implement whatever feature they want to it and no skin compatibility would be lost.

-Plague