- marked as bug
Blank Artwork Field In Save Set Erases Found Artwork
I have a bunch of Saved Sets where the artwork field is left empty on purpose, because I wish to pass through whatever artwork was found when I searched for metadata. Prior to version 1.2, an empty artwork field would not overwrite the artwork that was loaded from the metadata search, but now it does.
Would it be possible to make it so that the Artwork field being empty in a Saved Set behaves as "passthrough all artwork that exists currently" rather than "clear all artwork that exists currently"? Although, I see the benefits of having both options available, so could there be a method of choosing between the two options? Perhaps you could include a checkbox/switch with the options "Add Artwork" and "Overwrite Artwork" available to choose from?
The four behaviors would be:
-
If the switch is set to "Add Artwork" and the Saved Set's artwork field is empty, then it passes through whatever previous artwork existed in the field prior to applying the set.
-
If the switch is set to "Add Artwork" and the Saved Set's artwork field is filled, then it supplements whatever artwork existed prior, with the art in Saved Set. This allows for multiple images.
-
If the switch is set to "Overwrite Artwork" and the Saved Set's artwork field is empty, it clears all artwork after the set is applied so that you're left with a blank field.
-
If the switch is set to "Overwrite Artwork" and the Saved Set's artwork field is filled, the artwork in the set overwrites the previous artwork, leaving solely the art from the Saved Set.
The switch preference would be a chosen on an individual, per-Saved-Set basis.
I feel like I remember people going back and forth over which behavior they prefer. This would allow for everyone to be accommodated.
Thoughts?
Comments (7)
-
reporter -
repo owner - changed status to open
-
repo owner 1.2.2 should revert to the old behaviour.
-
reporter It does and doesn't.
Applying the Saved Set doesn't overwrite the obtained Artwork when done via drag-and-drop into the Queue, but it does on an individual basis when manually applying the Save Set to an individual file.
I really like and appreciate the addition in the Queue though!
-
repo owner That's what happens when I wrote the same code two times and forgot to update one of the two :|
-
repo owner 1.2.3 contains the missing part of the fix.
-
reporter - changed status to resolved
- Log in to comment