Bug 142813 - no clock while processing display with color management
Summary: no clock while processing display with color management
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: ColorManagement-Views (show other bugs)
Version: 0.9.1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-11 02:01 UTC by Régis R.
Modified: 2022-02-01 11:31 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Régis R. 2007-03-11 02:01:12 UTC
Version:           0.5.0 (using KDE 3.5.4, compiled sources)
Compiler:          gcc version 3.4.6
OS:                Linux (i686) release 2.6.20-1rrt

The mouse pointer doesn't look like a clock while showfoto is processing the display for color management (F12).
Comment 1 caulier.gilles 2007-03-11 08:43:50 UTC
Yes, agree

To be right, you talking about the color management _view_ option...

Gilles Caulier
Comment 2 Marcel Wiesweg 2009-08-23 20:57:57 UTC
On my machine, color managed view feels a bit sluggish but does not hang. Is it really really slow on some machines so that displaying a waiting cursor would be justified?
Comment 3 caulier.gilles 2013-11-27 13:32:15 UTC
Marcel,

I follow you : here i use CM view with my 27' monitors.

Loading a Sony A77 24Mpx JPEG file in editor, and switching CM with F12 is rendered immediately. There is no latency (i use LCMS2). My Screen profile have been processed manually with a ColorHug sensor (http://www.hughski.com/)

24Mpx is really a critical use case. It's a huge image resolution.

As it's an older entry, we can considerate this issue as obsolete. Also, we don't receive any feedback since a while.

Gilles Caulier
Comment 4 Régis R. 2013-11-29 21:54:54 UTC
I don't have/use proper profiles right now to check if the screen icon in the right bottom corner toggle at the beginning or at the end of the process.

If it's at the end, it's perfectly fine, because as I remember, the question was less the slowness than how to know for sure it's done, especially if you use the feature for the first times or you assemble a dozen images to make a big pano.