Summary: | Pick correct date from selected pictures when creating a new album | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Mickaël <mprizee> |
Component: | Albums-MainView | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | wishlist | CC: | caulier.gilles, chaofeng111, simon, sven.burmeister |
Priority: | NOR | ||
Version: | 1.3.0 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 5.1.0 | |
Sentry Crash Report: |
Description
Mickaël
2010-07-24 20:54:03 UTC
Which behavior do you expect? DigiKam should say there are no photos in the album, as it does when modifying an empty folder. Modifying works fine (cannot find a date because there are no photos) but creating seems bogued (find a date, I think from photos that are not in the album). I speak about the automatic dates (oldest, average, etc...) no about a date I would enter myself. Dates are read from the parent directory. That is because the dialog is written in the first place for changing properties, not for creating a new album. I think the bug is that digikam does not set the date for an empty, i.e. when creating a new album, even if it could because the user chose to download pictures to that new album. So expected behaviour would be: - The user picks some pictures to download into an album. - Digikam asks where to download to. - The user creates a new album and clicks on "earliest" or any other date funtion below the little calendar. - Digikam picks the correct date from the selected pictures which are not yet part of the album. Tested with Revision: 1165842 *** Bug 273642 has been marked as a duplicate of this bug. *** As i wrote in bug 273642, the dates of the selected images to import should be used, if parsing takes too long the creation dates would be sufficient Mickael, This file still valid using digiKam 2.x serie ? Gilles Caulier Michael, We need a fresh feedback using last digiKam 4.2.0 here... Gilles Caulier New digiKam 4.11.0 is available : https://www.digikam.org/node/740 Can you reproduce the problem with this release ? Gilles Caulier 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 |