[Feature Request]: Tag Management for multiple files [improvement]
Checklist
- [x] I am using an up-to-date version.
- [x] I have read the documentation.
- [x] I have searched existing issues.
Description
Tag Management for Multiple Files
Selecting multiple files currently results in a blank Tag area. Is this intended behavior? It would be helpful if selecting multiple files could display both common tags (shared across all files) and partial tags (present on some files).
Screenshots for clarity:
Single file selection shows tags as expected:
Multiple file selection shows blank Tag field:
Tags Window
The ability to add tags to multiple files is brilliant, could we also implement bulk tag removal? Perhaps using middle-click in the Add Tags window to remove tags?
(I did find the Manage Tags window Ctrl + M, but that ended up deleting the Tag from the database 😭)
Currently there's no visual confirmation when tags are added to multiple files in the Add Tags Window (Checking the background window Tags field works) Also note The Tags field in the background window only shows tag updates for single file selections, not when multiple files are selected.
Real-time tag updates
Note how the Tag field updates in real-time when adding tags (visible in the background window's Tag Field, right side):
Is it possible to display a checkbox next to the Tags in the Tags Window and the main window (Bottom Right corner) :
A check ☑️ if all the selected files have the Tag
A Dash ➖ Patrial Tag When some selected files have the selected Tag
An Empty 🟪 unchecked box when none of the selected files have the Tag added
I know the plus icon was just removed😶 (Thanks for removing the plus icon that was Awesome!!!) I prefer the latest implementation where the whole box/Tag can be clicked instead of a smaller plus box, I'd like to retain that behavior and include a tick box
This would give users both:
-
The convenience of clicking anywhere on the tag
-
Clear visual confirmation through the checkbox state
Thank you for taking the time to read this. Cheers!
Solution
No response
Alternatives
No response
Better handling of bulk/mixed editing is indeed something that I plan on adding and improving. This was something present to a degree in v9.4 but was plagued with issues (see #92). When the initial jump to a SQL backend was made this introduced an entirely different set of bugs when it came to mixed editing. When I worked on #655 as a way to fix some of the initial database flaws + refactor the preview panel to be more modular, I stopped short of properly implementing mixed editing since it was quite a large task to get right and the PR had already gotten much larger than anticipated at that point. So in a way this is half "bug" and half "feature request", but I certainly want to restore the old mixed editing functionality while improving upon it (see also #337).
Piggy-backing off this request, since I think this could also be nice for bulk editing;
Would it be possible to support -<tag_name> in the Add Tags panel?
Or is that not possible because - is not reserved as the start of a tag name?
Check out my duplicate issue (#811) for more ideas, if you want lol
Making this available for fields would be also very useful, for example, having used path search to limit entries for a particular artist, I I added the artist field to it, hoping it would create a popup where I can assign the same artist to all those selected, but now I have to go one by one and edit them, additionally, I created another artist field by accident, which means I have to delete it all one by one.
Given that this is how it looks when adding additional fields, fields that have the same type and value shared by all can have (All) next to the field type or (Mixed) iof it's only shared by a few.
This would also make it easier to later update/normalize those fields in the case where you have an artist that maybe changed their name, one can limit the search to that artist and mass edit it to the artists new name.
This... doesn't look like its been worked on in awhile (most of the "updates" are just dupe issues being removed)
seems like this one hasn't been touched directly since the last activity on my sister feature request ( #337 )
This function/bug is absolutely the biggest deal-breaker. Without a fast way to handle large numbers of tags, the efficiency is far too low.