| Summary: | Bad date in header | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | rom1v |
| Component: | Searches-Dates | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles |
| Priority: | NOR | ||
| Version: | 0.9.3 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 5.8.0 | |
| Sentry Crash Report: | |||
| Attachments: | screenshot of the problem | ||
|
Description
rom1v
2008-01-24 21:36:01 UTC
Sorry, not only in the the "Dates" tab, but also in "Album" tab. The header is not correct. Created attachment 23255 [details]
screenshot of the problem
This sounds related to http://bugs.kde.org/show_bug.cgi?id=130230 http://bugs.kde.org/show_bug.cgi?id=121460 (maybe it is even the same?) Arnd, Yes certainly. Before to release 0.9.4, we will review together all Dates bugzilla entries when TimeLine will be completed and ported to KDE4. Gilles Andi, You have not fixed recently this problem ? Gilles Romain, This problem still exist with digiKam 0.10.0 ? Gilles Caulier What is wrong in the attached screenshot? The problem I fixed was that it displayed September 2,008 instead of September 2008 But since I changed it to be more locale aware, the problem described here could be fixed now. Again, what is wrong in the screenshot? That the word is lowercase? Andi Oh now I see :-) The word means January, right? Well my patch didn't fix that. Andi Romain, I have been testing this report with current 1.0beta. I am getting that you have your albums named by date and that the album date does not reflect the date of the pictures. You expect the album date to be the same as the date it says in its name. Is that right? The displayed "album date" can be adjusted by context menu -> Properties. It is set at creation. How did you create these albums; which date do you expect the album date to take? What about this report? Any news? Romain, Do you see comment #9 from Marcel ? Gilles Caulier I'll close this one due to the lack of an reply from the original author... Also the issue was in the KDE3 version of digiKam... If the problem still exists, please open a new fresh bugreport for the KDE4 version of digiKam... This problem is not reproducible using current 5.8.0 pre-release bundle available here : https://files.kde.org/digikam/ I close this file now. Re-open it if necessary. Gilles Caulier |