Bug 391839

Summary: Grouped pictures no longer appear in albums, tags, searches or timeline
Product: [Applications] digikam Reporter: MarcP <iwannaberich>
Component: Albums-ItemGroupAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: caulier.gilles, iwannaberich, metzpinguin
Priority: NOR    
Version: 5.9.0   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed In: 7.0.0
Sentry Crash Report:
Attachments: Screenshot. Selection contains 7 items, but none are shown.

Description MarcP 2018-03-14 00:33:07 UTC
Created attachment 111386 [details]
Screenshot. Selection contains 7 items, but none are shown.

When grouping pictures, all but the first one appears in albums, tags, searches or timeline. The rest, even if in these sections they count as valid elements for the total number displayed, are invisible.

For instance, let's say 2 pictures from a 30 picture album were grouped with copies in another folder. In the treeview, the folder will still show the number 30, but only 28 will be displayed in the thumbnail view, with no indication whatsoever that there are 2 additional pictures somewhere.

Another example: After reorganizing some duplicated face tags, there's one tag still containing two elements, but none of them are shown when selected and cannot be found, as probably these two pictures are part of some group.

I think the correct behavior would be to show them, with the whole group if possible, when a tag or a folder or a timepoint is selected in the left panel. Right now that only happens for the picture on top of the group, not for the rest.

I've attached one screenshot as a sample. Notice how August 1947 is selected, containing 7 items, but none of them are shown in the thumbnail view, and at the bottom left it indicates "No item selected (0 items)".
Comment 1 Maik Qualmann 2018-03-14 06:04:40 UTC

*** This bug has been marked as a duplicate of bug 303239 ***
Comment 2 caulier.gilles 2020-01-19 09:49:19 UTC
Fixed with bug #303239