ML History View Column Heading Change

[Aminifu]

The column currently named "Title" in the history view doesn't display the file's title. It displays the playlist editor's string for the file that was played. I suggest the column's heading be changed to correctly indicate what is being displayed (or change the column's content to match it's heading).

[dro]

So what should the column name be? I am going to note that pretty much everything else I can see is using title for the pre-generated strings (main & library playlists, bookmarks, podcast downloads) & it's only the local library where there's a difference only due to how it's interaction with the lower level metadata.

-dro

[Aminifu]

"Playlist String" or something like that. I noticed this when I changed the PE ATF string I was using and saw that that column contents changed to match it. Older records used the previous PE ATF string. Not necessary, but would it be possible to add an option to update old records to match the active PE ATF string.

Since I'm using 3 different ATF strings in different places for the playing file, I've now changed the PE string to only show %title% and thus match the column heading in the history view.

Things could stay as they are, changes are not really necessary. Once I noticed this behavior and realized it wasn't an history view error in reading metadata, I decided to mention it.

[dro]

I get the potential for confusion but I also think that there's enough context between title as a metadata field & title as a formatted string for it to not be a problem & as such I'm not going to change the column name as that's then introducing more disparity into things vs existing usage of the term.

Will add the request to refresh the existing history titles to the todo list.

-dro

[Aminifu]

...

Will add the request to refresh the existing history titles to the todo list.

-dro

Thank you.

[dro]

This'll be done as a right-click option on the history node's context menu. Was debating having it be auto-applied but that was going to complicate things a bit more than I necessarily like to implement for the moment. It means another manual step but just having something for now much like with the library playlist refreshing should be enough when I'd expect for most that they don't need to refresh it too often.

-dro