Bug 333634

Summary: Text Filter : add new option in text filter combobox to apply AND or OR operator between terms
Product: digikam Reporter: Cluey <cluadiacapella>
Component: Albums-FiltersAssignee: Digikam Developers <digikam-bugs-null>
Status: REPORTED ---    
Severity: wishlist CC: caulier.gilles
Priority: NOR    
Version: 3.5.0   
Target Milestone: ---   
Platform: Ubuntu Packages   
OS: Linux   
Latest Commit: Version Fixed In:

Description Cluey 2014-04-19 20:36:48 UTC
Hello!   I have been troubled by the semi-recent change to the way spaces behave in the text filter.  Prior to this change, they used to behave as OR instead of AND.   
(Typing "n.Ne t.bl" would result in a file that had the tags Human.Ned and Coat.Black.   Now it results in nothing as soon as you hit space)

I am requesting that it is worth the UI real estate price to have a checkbox in preferences to toggle between OR and AND for the text filter.

Digikam used to be a program which I could find any file I wanted out of half a million within 3 seconds, but with this change, I can't figure out any way to find the same files in less than half a minute, and the text filter is only good for finding one tag at a time, which is disappointing to how powerful it was before.   Are there any other ways to achieve such file finding speed? 

Thank you!

Reproducible: Always

Steps to Reproduce:
1. Make 2 tags for a file.  (Human.Ned, and Coat.Black).  
2. Type a few letters of the first tag, press space, and type a few of the next  (n.ne t.bl)

Example 2, with a filename of "What is a Lommy.jpg"
1. Type the first few letters of a filename, followed by a space, then the last few letters of the filename.  Example: "wha mmy"
Actual Results:  
In both scenarios, the file you are trying to find will be filtered out, since spaces has been changed to AND instead of OR.   As soon as you press space, the file should be filtered out.

Expected Results:  
Typing "n.ne t.bl" should allow a file with the tags "Human.Ned" and "Coat.Black" instead.

Is there any way for me to change this currently without hoping for this wish to come true?  Perhaps a way to compile the source for it that someone pretty stupid compiling sources could do?   

While I'm throwing out suggestions
1. I am forced to tag without heirarchies, because the text filter does not allow them.  (Example: a tag of Human/Jon.   You can't type in an/Jo, since the text filter doesn't respect using / as a heirachy.     Therefore, I am forced to make long tags, ie:
Animal.Human/Human.Jon Snow/Jon Snow.Clothing/Clothing.Coat/Coat.Black
Instead of
Animal/Human/Jon Snow/Clothing/Coat/Black

2. Combine this with some kind of easy way to denote a NOT, such as |n|(tag name) or so, and I'd never need to venture into the dreaded advanced search window again.

Thanks again
Comment 1 Justin Zobel 2021-03-09 05:51:46 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.