[Digikam-devel] [Bug 148382] overexposure indication already when fully "saturated"

Jens Mueller tschenser at gmx.de
Mon Jan 4 18:46:26 GMT 2010


https://bugs.kde.org/show_bug.cgi?id=148382





--- Comment #13 from Jens Mueller <tschenser gmx de>  2010-01-04 19:46:24 ---
Hmm, quite a good question. My thoughts on this:

When we are looking at HSV color interpretation we have Color, Saturation and
Value. Value (between 0.0 and 1.0) shows the lightness of a pixel, so I think
this is the one. A Value of 0.0 meens underexposed and a value of 1.0 meens
overexposed. 
When will Value be 0.0? If all RGB components are 0.
When will Value be 1.0? If one of the RGB components is max.

Following this argumentation we should have (R=0 && G=0 && B=0) for
underexposure and (R=max || G=max || B=max) for overexposure.

But I dont know yet how other applications handle this.

Jens

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Digikam-devel mailing list