https://bugs.kde.org/show_bug.cgi?id=285521--- Comment #7 from Andreas Ferber <af+kde chaos-agency de> 2011-11-02 20:12:59 ---
Hi,
Even disregarding the granularity, timeline (or the date range search options
in advanced search) isn't really what I want. In more general terms, I want to
(almost) arbitrarily mask out certain parts of the timestamp and match against
the remaining bits.
To give another example, suppose you want to find all pictures you have ever
taken during winter. Sure, you could set timeline to month granularity and
manually select December, January and February in each year you have pictures
from. For one or two years, this would be somewhat manageable, but think about
10 or 20 years... And even then, you couldn't combine this with other criteria
(at least without a boatload of ORed together criteria in advanced search).
With my proposal, in advanced search you would select "Month only" as the
timestamp part, enter the three winter months from above (multiple select
maybe?), and be done with it, regardless if your collection spans 1, 10 or 100
years.
You could maybe add some sort of season tags to your photos, but why do it if
the timestamp already contains this information? And what if tomorrow you would
like to find pictures from around christmas? Add that as a tag as well?
I hope those examples show what a versatile search feature this would be, much
more than the current "date range" or timeline approach.
Andreas
--
Configure bugmail:
https://bugs.kde.org/userprefs.cgi?tab=email------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Locked
