Bug 273642 - dates of selected images not used in new album when importing
Summary: dates of selected images not used in new album when importing
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Albums-MainView (show other bugs)
Version: 2.0.0
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-19 14:54 UTC by simon
Modified: 2021-05-08 12:58 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 7.3.0
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description simon 2011-05-19 14:54:10 UTC 
Version:           2.0.0 (using Devel) 
OS:                Linux

hi,

when i select images of a trip in e.g. February 2011 i want creat a new album from it and set the date correctly

using oldest/average/newest doesn't change the proposed date of the album

Reproducible: Always



Expected Results:  
oldest would use date of first selected image to import
average -> average
newest-> newest

OS: Linux (x86_64) release 2.6.38.6-zen-01981-ga3c54ec
Compiler: x86_64-pc-linux-gnu-gcc
Comment 1 Marcel Wiesweg 2011-06-11 17:02:40 UTC 
How exactly do you create the new album?
Comment 2 simon 2011-09-25 10:14:57 UTC 
i do it like this:

- "import"
- select images 
- "download"
- album selection pops up
- select my root images folder 
- click "create new album"
- fill in title, category
- current date is preselected
- i want the album have the date of the first/last/average image dates to be imported, mybe the image dates of the whole collection is used?
Comment 3 Marcel Wiesweg 2011-10-29 12:57:41 UTC 
It's a flaw in the implementation of the dialog.
Still not easy to solve because getting the date of the new images would first require to parse them, which may take long (scales linearly)

*** This bug has been marked as a duplicate of bug 245678 ***
Comment 4 caulier.gilles 2021-05-08 12:58:27 UTC 
Fixed with bug #245678