[digikam] [Bug 435695] Publish image quality information

https://bugs.kde.org/show_bug.cgi?id=435695 --- Comment #2 from hann...@hot.ee --- Proposal. 1. Algorithm side. The numerical results of the image quality sorter could be stored under Digikam properties and recalculated only if the calculation algorithm is changed. If a new image is added, the

[digikam] [Bug 435695] New: Publish image quality information

https://bugs.kde.org/show_bug.cgi?id=435695 Bug ID: 435695 Summary: Publish image quality information Product: digikam Version: 7.3.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED

[digikam] [Bug 435564] The similarity finder uses about half the CPU clock speed

https://bugs.kde.org/show_bug.cgi?id=435564 --- Comment #11 from hann...@hot.ee --- Thanks for the answers. I understand that the search for similarities must work that way. Hannes -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 435564] The similarity finder uses about half the CPU clock speed

https://bugs.kde.org/show_bug.cgi?id=435564 --- Comment #8 from hann...@hot.ee --- It is strange that during the operation of DK similarity and other resource-intensive processes, the CPU clock speed decreases from the maximum to 54-75%. At the end of the process, it rises to the maximum.

[digikam] [Bug 435564] The similarity finder uses about half the CPU clock speed

https://bugs.kde.org/show_bug.cgi?id=435564 --- Comment #1 from hann...@hot.ee --- Created attachment 137464 --> https://bugs.kde.org/attachment.cgi?id=137464=edit Open Hardware Monitor -clock bus speed -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 435564] New: The similarity finder uses about half the CPU clock speed

https://bugs.kde.org/show_bug.cgi?id=435564 Bug ID: 435564 Summary: The similarity finder uses about half the CPU clock speed Product: digikam Version: 7.3.0 Platform: Microsoft Windows OS: Microsoft

[digikam] [Bug 435541] Cannot delete "Current search" from 8 "Current Search" labels.

https://bugs.kde.org/show_bug.cgi?id=435541 --- Comment #3 from hann...@hot.ee --- (In reply to Maik Qualmann from comment #1) > Normally the "Current search" should only be available once, it cannot be > deleted. It was reported a long time ago that several "Current searche" can > arise, so far

[digikam] [Bug 435541] Cannot delete "Current search" from 8 "Current Search" labels.

https://bugs.kde.org/show_bug.cgi?id=435541 --- Comment #2 from hann...@hot.ee --- Only first "Current Search" is working as expected. Others are freezing and are like "ghosts". If I save some searches- from first - they are perfectly functional. Unable to create additional Current Search labels

[digikam] [Bug 435541] New: Cannot delete "Current search" from 8 "Current Search" labels.

https://bugs.kde.org/show_bug.cgi?id=435541 Bug ID: 435541 Summary: Cannot delete "Current search" from 8 "Current Search" labels. Product: digikam Version: 7.2.0 Platform: Microsoft Windows OS: Microsoft

<    1   2