| Summary: | calendar view/digikam date does not update when exif dates changed externally | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Rich Lott <rl6> |
| Component: | Searches-Dates | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles |
| Priority: | NOR | ||
| Version: | 0.9.2 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 5.1.0 | |
| Sentry Crash Report: | |||
| Attachments: |
Settings for changing the date and time in digiKam
screenshot of problem |
||
|
Description
Rich Lott
2008-05-10 21:15:48 UTC
When I change the date of an image in the EXIF header, I have two entries: "date and time (modified)" and "date and time (original)". DigiKam seems to take the original time which will not change (well it did not on my system). So when you want to change the date and time for some images, you should do this directly in digiKam: 1. select the images you want to change 2. from the menu select Image->Metadata->Edit EXIF 3. Go to the date and time tab and edit the settings (I will add a screenshot to show you the settings needed) 4. After that, the database will be updated and the date view is correct again. This should fix your "problem"... Created attachment 24921 [details]
Settings for changing the date and time in digiKam
Created attachment 24936 [details]
screenshot of problem
I've attached a screenshot of the problem (for clarity's sake, but I think you
understood anyway)
I appreciate your help, but I was really reporting it as a *bug* that should be
fixed, it actually doesn't bother me much (in this instance) that digikam shows
the image on the wrong date.
Also, a quick fix is to externally rename the folder, eg. append a _, then
digikam will have to reindex the files as it thinks it's new.
I might try the digikam GUI for changing the dates if I need it in future, but
it really should work interoperably with other software, so I do hope that
someone is interested in fixing this (albeit non urgent!) bug at some point.
Rich.
Rich, What the problem with your screenshot ? date is the same in Exif viewver from the right and Exif editor dialog... Gilles Caulier It is a bit of a spot the difference, I admit! The problem is that despite what you've pointed out (and -not shown- that the file mtime is also the same date), digikam lists it under 11 May, (see bottom left red circle) instead of 10 May. See original bug report above. thanks. Rich Rich, can you still confirm this bug in digiKam-0.10 or digiKam-1.0.0-betaX ? Hi Andi I'm running the latest LTS Ubuntu, i.e. Hardy, and according to http://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg1266275.html "There are no Digikam 0.10.0 packages for Hardy." I couldn't find a ppa deb archive anywhere, and I'm not really up for compiling it as I suspect that would be a beast of a job. Willing if you say it's easy... So can't confirm. Many thanks for your interest, though! rich Andi Clemens wrote: > https://bugs.kde.org/show_bug.cgi?id=161922 > > > > > > --- Comment #6 from Andi Clemens <andi clemens gmx net> 2009-10-09 13:33:53 --- > Rich, > > can you still confirm this bug in digiKam-0.10 or digiKam-1.0.0-betaX ? > > Rich, This entry still valid with 2.x release ? Gilles Caulier Rich, We need a fresh update here. Do you tried digiKam 3.x release ? Gilles Caulier New digiKam 4.11.0 is available : https://www.digikam.org/node/740 Can you reproduce the problem with this release ? With digiKam 5.0.0, this problem is not reproducible. I close this file now. Don't hesitate to re-open if necessary. Gilles Caulier |