Support for two additional options in the "Select Closest Matches" dialogue

[touwys]

@Borewit, thank you again for your work on listFix() release v2.8.0.

Please take a look at the included annotated screenshot. It is a request for the support of two more options, which are to be provided in the context menu of the "Matched Name" column of the "Select Closest Match" dialogue. Both of these options will overturn the stalemate evident when no matches, or unapproved matches, are found. Especially so, when the user is editing long, broken playlists.

Thank you.

• Select ClosestMatches' Dialogue — Add Options
  

[touwys]

Can #188 be classified as low-hanging fruit? As with #194 and #196, and instead of other issues, attending to #188 would provide a huge step ahead for the enhancement of playlist repair operations. In particular, as far as enhancing "Select Closest Matches", because the user has to abandon the "Select Closest Matches" after its processing is completed — as soon as it is apparent that of all the closest match that were found, not everyone is a suitable match for the expired track.

Additional Comments

Please read this in conjunction with the original post for context. Small differences may be apparent between them, but overall it should still make sense. If not, please, please advise for correction:

Enhance the "Select Closest Matches" dialogue by adding two basic, very useable functions via the track context menu in the "Original Name" column and "Matched Name" column.

1. Add "Copy name" to the context menu of tracks in both columns. When using alternative methods to manually search for matching tracks, the copy-and-paste action would nicely enhance the ease of search for suitable replacement tracks.

2. Add to the context menu of any track selected in the "Matched Name" column, the option to, for e.g. "Choose a match" or "Locate a match", or something similar, [in addition to "Skip this match" as per screenshot in the original post]. The idea is that this should open the OS file manager, allowing the user to find/locate any alternative track of his choosing, or alternatively, to skip the found match, altogether.

Number 2 is the more important from an operational perspective.

• Screenshot 1:
  

• Screenshot 2:
  

[Borewit]

Can #188 be classified as low-hanging fruit?

Maybe those fruits look delicious, but they don't hang that low.