Bug 151972

Summary: Color Management shows repeatedly error messages on resizing
Product: [Applications] digikam Reporter: Thomas Thrainer <tom_t>
Component: Plugin-Editor-ColorManagementAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: caulier.gilles, rharrison
Priority: NOR    
Version: 0.9.2   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In: 1.0.0

Description Thomas Thrainer 2007-11-07 10:34:51 UTC
Version:           0.9.2-final (using KDE KDE 3.5.8)
Installed from:    Ubuntu Packages
OS:                Linux

I open an image for editing.

Then, I chose Color->Color management... (Farbe->Farbverwaltung in German), and I get an error message that my settings are not sufficient (it says that I need an input- and and output-profile).

I am fine with this error message, altough it is displayed before I even had the change to change the settings.

But, once clicked on "OK", the dialog opens. When I resize the dialog, for each time the dialog gets redrawn (I suppose), The very same error message occurs again. So it is very easy to end up with 5 error message dialogs at the same time, all saying the same.
Comment 1 Andi Clemens 2008-09-01 10:07:31 UTC
Right now the only possibility is to remove the connection on the resizeEvent that will always re-open the info dialog. But this is not a good solution.
Maybe a better approach would be to disable the Color Management plugin if "Color Management" is not enabled in the general digiKam settings?

Andi
Comment 2 caulier.gilles 2008-12-06 18:02:43 UTC
Andi, 

Something is bad designed into this plugin. It can be simplified, i'm sure.

Gilles Caulier
Comment 3 Andi Clemens 2008-12-06 19:41:14 UTC
Yes, maybe. It's been a while since I took a look on this...

Andi
Comment 4 Andi Clemens 2009-09-29 22:58:26 UTC
Same question as for bug 131948: Can we close this?
Color Management plugin has been re-written, and I can not confirm this anymore.
Comment 5 Andi Clemens 2009-10-15 14:04:16 UTC
I will close this one now, since we don't seem to use IICProofTool anymore.