Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Context menu ordering of those populated with data from library/config (Read 17 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Context menu ordering of those populated with data from library/config

I currently use an embarrasingly ancient version of foobar 1.3.16, and it serves me well but I was wondering about an issue that often limits my configuration patience, and sadly I'm pretty sure of what the answer I'm looking for will be.

For context menus that supply all the playlists in the library (exclusive to user components I'm assuming) they are always listed in the order of creation. Choosing a desired playlist for actions when you have way too many playlists is virtually impossible. Same goes for components that display a dropdown for playlist selection of a configuration option. This presents itself as a frustrating issue using both the default playlist viewer and ESplaylist, as well as any component sending tracks to other playlists. Sorted alphabetically with a seperated section at the top that is manually ordered would be ideal for presenting both data.

Similar with the default UI, if you have many custom columns created, they are also listed in order of creation when toggling visibilty. Also the same when configuring custom columns, they are listed the same and can't be sorted to identify duplicates, or making higher priority or more frequenly toggled columns at the top. If the table was sortable the same way keyboard shortcuts is, with ability to move a selection up/down in the order would be quite helpful.

I'm guessing the only available solution is a scripted playlist viewer to replace both, but what I'd like to know before I bother migrating to the latest version, could somebody tell me has this already been addressed in the latest version, or the likelyness this configuration creativity drawback will be fixed someday?