[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 148382] overexposure indication already when fully "saturated"
From:       Alexander Neundorf <neundorf () kde ! org>
Date:       2007-08-02 2:39:07
Message-ID: 20070802023907.10730.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=148382         




------- Additional Comments From neundorf kde org  2007-08-02 04:39 -------
I should really try current svn...

Anyway, changing the following line from:
 if (expoSettings->overExposureIndicator && 
     pix.red() == max && pix.green() == max && pix.blue() == max)

to 

 if (expoSettings->overExposureIndicator && 
     pix.red() == max || pix.green() == max || pix.blue() == max)

might be a good idea, so you will also catch areas where only one channel is \
overexposed, which also leads to bad colors, e.g. if you have an area where green \
would go from 200 to 400 and red and blue from 125 to 250, which would be a bright \
green gradient, you will instead get a change from bright green to white, since green \
can't go beyond the 255. Detecting these areas too would show this problem.

Not quite sure about underexposure...


[prev in list] [next in list] [prev in thread] [next in thread]