Bug 195817 - No progress information is shown when applying tag changes to a _single_ image
Summary: No progress information is shown when applying tag changes to a _single_ image
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: ProgressManager-Batch (show other bugs)
Version: 0.10.0
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-09 21:05 UTC by Michael Liddle
Modified: 2022-02-05 15:57 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.6.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Liddle 2009-06-09 21:05:33 UTC
Version:           0.10.0 (using 4.2.88 (KDE 4.2.88 (KDE 4.3 >= 20090527)) "release 127", KDE:KDE4:Factory:Desktop / openSUSE_11.0)
Compiler:          gcc
OS:                Linux (i686) release 2.6.25.20-0.4-default

When editing the tags of a _single_ image, and either when pressing the "Apply" button or (if "do not confirm when apply changes" in the right sidebar is active) navigating away from the current image, digikam appears to "freeze" for a second or with no indication of what it is doing (presumably writing the changes of course, which for me involves writing over a network). This is especially obvious in the latter case of navigating away from the image, and is a little disconcerting.

For changes to _multiple_ files, a progress bar is shown, and everything appears to function fine.
Comment 1 Richard Ash 2009-12-28 20:47:51 UTC
This is easy to reproduce on a local disk by picking a image format where re-writing the tags requires the whole image to be read and re-written to disk, and using reasonably large images - 4MB JPEG2000 files do it quite noticeably when editing the captions.
Comment 2 caulier.gilles 2011-12-16 12:29:28 UTC

*** This bug has been marked as a duplicate of bug 284212 ***
Comment 3 caulier.gilles 2022-01-22 16:52:09 UTC
Fixed with https://bugs.kde.org/show_bug.cgi?id=284212