| Summary: | Digikam searches for sidecar files even though reading them is disabled | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Theliel <tahariel> |
| Component: | Metadata-Sidecar | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | normal | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 7.5.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed/Implemented In: | 7.6.0 | |
| Sentry Crash Report: | |||
|
Description
Theliel
2022-02-14 23:32:19 UTC
I'll debug it tonight, but I'm pretty sure digiKam won't look for sidecars during startup scan if the option is disabled. A quick look at the code confirms this. If you select a single image in the GUI and have the Properties tab open, it will look for a sidecar. This is intentional because the property is intended to show whether the image has a sidecar, regardless of the setting to read or write sidecars. Maik It can be a rule in Exiv2 engine where we don't have a control in digiKam side... Gilles Thanks for the support. It seems to happen only when selecting an image, no matter if the properties panel is open or closed A search for a sidecar only occurs when the Properties tab is selected, regardless of whether the sidebar is collapsed or expanded. This behavior is desired because we want to indicate whether a sidecar exists. This is not a loss of performance, it is only searched for when a file is selected individually. There are more sidecar searches when copying and moving images. We need to make sure that if sidecars are present, they are also copied/moved. Otherwise they would be left orphaned, regardless of whether sidecars are activated or not. I close the bug, the behavior is technically necessary. Maik |