Bug 192454 - Allow setting of start or "pivot" time for a day
Summary: Allow setting of start or "pivot" time for a day
Status: REPORTED
Alias: None
Product: digikam
Classification: Applications
Component: Searches-Dates (show other bugs)
Version: 0.10.0
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-12 17:19 UTC by DGardner
Modified: 2021-03-09 05:51 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description DGardner 2009-05-12 17:19:33 UTC
Version:           0.10.0 (using KDE 4.2.2)
OS:                Linux
Installed from:    Ubuntu Packages

If I take photos at a party, I'll often have photos from either side
of midnight. When I use the calendar view in digiKam, I can pick a
day and view images for that day. However, images that are related
to an event on a particular "day" (in the looser sense of the word)
are split over two days. In essence, digiKam assumes that I go to
bed before midnight, but sometimes I don't.

It would be nice if I could set a custom "pivot time"[*] to indicate
when I feel one day ends and another days starts. At present, the
pivot time is always midnight. However, a time like 0500 (5am) would
suit me better--I'm too old to stay up that late and too lazy to get
up that early. Then, if I click on, say, May 12, 2009 in the calendar,
I will see images from 05:00:00 May 12 to 04:59:59 May 13 instead of
just midnight to midnight on May 12.

At present, I get around this issue by tagging photos with an "event"
tag like "Events/Wedding/Alice & Bob" and then just selecting a whole
month and a tag filter. Supporting a pivot time sound like it would
be easy enough and would make browsing by date more "human". It would
also make it easier to select the new photos before I have tagged any
of them.


[*] A "pivot year" was a concept used to solve (or cause) lots of those
Y2K bugs where years were stored as two digits. If the system's pivot
year was set to, say, 25, then the range of any two-digit year was
assumed to be within 1925-2024, so "99" was "1999" and not "2099".

TV listings also use a pivot time that is not midnight.
Comment 1 DGardner 2009-05-12 17:20:25 UTC
Sorry, meant to mark that as a wish, not a bug. I can't see how to change it now.
Comment 2 Justin Zobel 2021-03-09 05:51:32 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.