|
Now that I think about it, wouldn't that do the same thing as "copy to new value"? I might be confused. Oh my gosh, I feel stupid now. I didn't even see the "copy to new value" setting. But I guess this highlights a bit of the confusion over what you can do driven from column 1 vs column 2. Why don't we try and make this context menu the same for the whole row (not column dependent); and make it obvious what it's effecting? If it were named "Reset new value to original value" you could call it the same thing across all columns and then unify the context menu, right? Well you bring up a good point, that it's confusing to have these column-dependent menus. It should be accessible from both. "Reset new value to original value" is a good way to unify it, though I'd prefer something a bit shorter like "{use,keep} original value," unless you feel that sacrifices clarity too much. Yeah, was trying to think of something shorter. "Use original value" is probably sufficient, yeah. |
||||||||||||||||||||||||||||||||||||||||||||||||||
Ideally I'd prefer letting users manually remove existing tags regardless of clear_existing_tags, but it's hard to implement.
I see what you mean about the "reset to original value" idea. There's actually a new setting that prevents Picard from modifying certain tags now, but there should be a manual override in the metadatabox too. I'm in favor of adding "reset to original value" to the context menu there.
How about this option is separate from "remove," and is only available when you right click an existing tag that's being changed (yellow)? It could possibly be named "ignore this change," but your suggestion is fine too.