Filter Selection Behavior Malfunction
Wes Stephenson
wes_ws at hotmail.com
Sun Dec 7 14:54:26 GMT 2025
I previously posted about this problem, but I'm reposting to attempt to make it more clear.
I'm experiencing a Filter problem. It appears Digikam is somehow selecting items I didn't select. It occurs in 9 of my 63 Year Albums and Tags. Here is a description of behavior as brief as I can make it. Sorry it is so detailed.
I have albums (directories) by years. I created a Event tag tree for each year. My tag tree looks like this...
> Tag
> Events
> Year
> Event Name
The actual tree I'm writing about is the 2004 Events, which looks like this.
> Tag
> Events
> 2004
> 2004-02-21 - Greenway Rollerblading
> 2004-04-09 - Pilot Mountain Family Hike
> etc.....
> 2004 Not Currently In Event
> 2005
> etc...
My problem is when I attempt to identify photos in a year that are NOT assigned to a specific event. I tag these photos as "Not Currently In Event" so I can then see my "excess" photos that could be parsed to events later. In that way, I have tagged ALL my photos for that year into an "Event" of "Non-Event".
Here is process to do this which works for most of my tag trees.
1. Select an Album for a year, which is found under Tag > Year, a higher level and different part of my tag structure than the Events subtag section. (see "Step 1.jpg").
1. Select all Event check boxes for that year using the Filter tab at right.
1. Select all filtered photos using Ctrl-A. (see "Step 3jpg")
1. Select the year tag box at top of the Events tag tree shown above. The non-event photos show as well. Ideally, all photos for that year appear with only the photos which are assigned to an Event highlighted. (see "Step 4.jpg" for this 2004 malfunction year).
THIS IS WHERE THE PROCESS GOES WRONG FOR 9 OF MY YEAR TAG TREES. For my 2004 Events tag tree, I selected 1014 (see "Step 3.jpg). 2004 in total had 1108 photos (see Step 1.jpg). When I click 2004 to try as see the Non-Event photos as well, Digikam indicates that 1104 of 1108 photos are not selected (see "Step 4.jpg)
DIGIKAM SELECTED AN ADDED 90 PHOTOS, which includes 90 of the 94 Non-Event photos. Therefore, I am unable to isolate the Non-Event photos in these 9 seemingly malfunctioning tag trees.
For my other Year Event trees, I would proceed with these next steps to identify the Non-Event photos.
1. With all year photos shown, and only event photos highlighted, I select Invert Selection. The Non-Event photos will be highlighted instead.
1. Add the now-highlighted photos to the "Not Currently in Event" tag.
1. Now all photos in a year are assigned either to an Event or the tag "Not Currently in Event", so all photos of the year are categorized.
I have closely examined these malfunctioning event tag trees and can find NO difference in the tagging that the properly functioning event tag trees.
I'm stumped and will stop here.
Are there any ideas what is causing this behavior? Does anyone have a suggestion how to troubleshoot and solve this?
Thanks so much in advance!
Wes
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20251207/3526d98b/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Step 1.jpg
Type: image/jpeg
Size: 2949 bytes
Desc: Step 1.jpg
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20251207/3526d98b/attachment-0003.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Step 3.jpg
Type: image/jpeg
Size: 4787 bytes
Desc: Step 3.jpg
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20251207/3526d98b/attachment-0004.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Step 4.jpg
Type: image/jpeg
Size: 4481 bytes
Desc: Step 4.jpg
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20251207/3526d98b/attachment-0005.jpg>
More information about the Digikam-users
mailing list