[quote="rivorson"]Thinking about it, it would probably be even better to replace the context menu with a single item to send to a playlist which would then bring up a dialogue asking which playlist to save to. Navigating a treeview object is easier and faster than navigating a context menu.[/quote]

Yeah, that's closer to what I was thinking. You could have the popup dialog be like the classic "browse folders tree dialog" common in so many
programs, including MM, except it would only contain the playlist structure. You could just click around for what you want to send to.

Context menus mean well but they are difficult to navigate. You have to move the mouse up and down or over right with a high a degree of precision.
The slightest little wrong direction or too far movement causes the submenus to disappear and you have to reposition to get it to come back. Not so with
a browse dialog.

I definitely don't want anything that pre-constructs or suggests a new list like [i]Classic Jazz[/i] or [i]Modern Jazz[/i]. That gunks up the list with what could just be
"in the way" unused stuff. Reminds me of the "unused genres" issue. Or, were those just examples of possible lists someone might happen to have?

Thinking about it, it would probably be even better to replace the context menu with a single item to send to a playlist which would then bring up a dialogue asking which playlist to save to. Navigating a treeview object is easier and faster than navigating a context menu.

Half way there. If the two playlists are Just Jazz and Not Jazz, then the Just Jazz playlist has two children for modern and classic jazz then the structure would be like this:

Playlist
-Send to New playlist
-Just Jazz
--Modern Jazz
--Classic Jazz
-Not Jazz

Ideally clicking on Just Jazz would send to that playlist even though it has a sub menu. That may not be possible in which case it would still be necessary to go through a sub menu for playlists that have children but it wouldn't be necessary for playlists that do not have children.

It's basically the same structure as already exists but would show a submenu only if the playlist already has children. There would only be the main item for "Send to New playlist" which would then allow the user to select a location for the new playlist at the same time as giving it a name.

Then as an advanced feature you could Ctrl+Click on an existing playlist menu item to create a new playlist with the item you have clicked on pre selected as the parent location.

Personally I think that would be tidier.

rivorson,
So you are saying, have just "Send to Not Jazz" and after choosing it, the tree dialog pops up for you to input what you need?

Here's a quick and dirty mock up:
https://www.dropbox.com/s/qroe58d7ixupkew/NewPlaylist.png?dl=0

How about just having one item to create a new playlist then in the dialogue for entering the name have a tree view to select the new playlist's location?

I get it, but what about calling the submenu item "Send to Not Jazz new subplaylist" or "... sublist"
The way it's stated makes it sound like it's just an option for a new palylist, without any subcontext (even though it's in a submenu).

We can't just cut off, what if you want to add that tracks into new sub playlist of selected playlist?

But it asks twice "Send to new playlist" ... just cut off that last menu

Ok I agree it is a bit strange and how to solve Add new sub playlist then?

Maybe by adding all sub playlists to send to new playlist button and that > is shown only when playlist contain another set of sub playlists?

as you can see from the image you have to select the playlist twice ... just once is enough. should work like mm4

[img]http://i.imgur.com/ddIEUJA.jpg[/img]