Summary: | digikam 6.2-git win64 does not show some images in the folder | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Andrius <aegoreev> |
Component: | Albums-IconView | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | caulier.gilles, metzpinguin |
Priority: | HI | ||
Version First Reported In: | 6.2.0 | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
Latest Commit: | https://invent.kde.org/kde/digikam/commit/982c1c1146317253ebb5119770d665cdd6e5bdd0 | Version Fixed In: | 6.3.0 |
Sentry Crash Report: |
Description
Andrius
2019-08-03 12:13:00 UTC
Build date of my installation is July 14th ==> did you compile yourself digiKam or you use the windows installer ? Gilles Caulier (In reply to caulier.gilles from comment #1) > Build date of my installation is July 14th ==> did you compile yourself > digiKam or you use the windows installer ? > > Gilles Caulier Gilles, I used your installer. If I right click on the album in the folder tree and export to Google Photos I see that all the images are on the list. OpenGL Image Viewer displays all the images as well. So I think there is a possible bug with how the images displayed in album view. I tried Table view and I also tried playing with all Sort settings in View menu but it has not changed anything. I do not think that it is a bug in digiKam-6.2.0, probably the images would not appear even with digiKam-6.1.0. One way that could produce this effect would be to have an album-spanning grouping done. Then you have to find the leader image and dissolve the group again. Maik (In reply to Maik Qualmann from comment #4) > I do not think that it is a bug in digiKam-6.2.0, probably the images would > not appear even with digiKam-6.1.0. One way that could produce this effect > would be to have an album-spanning grouping done. Then you have to find the > leader image and dissolve the group again. > > Maik Maik, You are correct about 6.1.0 I am wondering how do I ungroup the images now. (In reply to Maik Qualmann from comment #4) > One way that could produce this effect > would be to have an album-spanning grouping done. Then you have to find the > leader image and dissolve the group again. Maik, I am not sure how to do that. I only see 2 images of 28. I tried to group/ungroup them but nothing happens... Would you have any idea on how do I make the images visible again? Do you use SQLite or MySQL as a database? Do you use grouping in digiKam or not? Maik (In reply to Maik Qualmann from comment #7) > Do you use SQLite or MySQL as a database? Do you use grouping in digiKam or > not? > > Maik I use SQLite. The only grouping I use is 'group by filename' on DNG/JPG pairs. These particular images are JPG only though. I don't know if is relevant but I got these images from a photographer and I noticed the photographer used Adobe Lightroom to create them. Git commit 1a5cf4a7885868a70e5ed07ab4ff4b4a7c80de9a by Maik Qualmann. Committed on 05/08/2019 at 18:57. Pushed by mqualmann into branch 'master'. add "Reset Grouping" option to the album context menu M +30 -0 core/libs/album/treeview/albumselectiontreeview.cpp M +2 -0 core/libs/album/treeview/albumselectiontreeview.h https://invent.kde.org/kde/digikam/commit/1a5cf4a7885868a70e5ed07ab4ff4b4a7c80de9a This new option in the album context menu resets all groupings in the selected album. We'll see if it's the cause with the next pre-release. Maik You can test this version of my GDrive: https://drive.google.com/open?id=11OqmZODKOeVABvVHEb4NulxTpxxmIyxm ---------- Compute package checksums for digiKam 6.3.0-git File : digiKam-6.3.0-git-20190805T223602-Win64.exe Size : 171M MD5 sum : a5d97934f75faca1db3ff74d5920e487 SHA1 sum : 3b2b61b452733ddbeefdd982c2dd89204a98b06c SHA256 sum : 1576c006691b39dce689d4d4d970adce31f422800acbbeb4acb8816e858b1d8e Maik (In reply to Maik Qualmann from comment #11) > You can test this version of my GDrive: > > https://drive.google.com/open?id=11OqmZODKOeVABvVHEb4NulxTpxxmIyxm > > ---------- Compute package checksums for digiKam 6.3.0-git > > File : digiKam-6.3.0-git-20190805T223602-Win64.exe > Size : 171M > MD5 sum : a5d97934f75faca1db3ff74d5920e487 > SHA1 sum : 3b2b61b452733ddbeefdd982c2dd89204a98b06c > SHA256 sum : 1576c006691b39dce689d4d4d970adce31f422800acbbeb4acb8816e858b1d8e > > Maik Maik, digikam 6.3.0-git Build date: Aug 6 2019 It worked. I think I know what happened. I think I grouped "web" and "full_resolution" versions of each image and then moved some of the images from the pairs to another folder outside of digiKam. I was not able to reproduce it though. So it is probably the user error as usual :-) Actually I did reproduce it. To reproduce try to: 1. group IMAGE-1 and IMAGE-2 2. then in Windows File Explorer move the image from the top of the stack e.g. IMAGE-1 to another folder 3. Refresh the album in digiKam 4. Move IMAGE-1 back to the original folder 5. Refresh the album in digiKam again Git commit 982c1c1146317253ebb5119770d665cdd6e5bdd0 by Maik Qualmann. Committed on 11/08/2019 at 10:27. Pushed by mqualmann into branch 'master'. give the user a hint in status bar if items are hidden by grouping or versioning FIXED-IN: 6.3.0 M +2 -1 NEWS M +18 -2 core/app/main/digikamapp.cpp https://invent.kde.org/kde/digikam/commit/982c1c1146317253ebb5119770d665cdd6e5bdd0 |