KColor is coming this Monday...

[Dominik Haumann]

On Friday 25 May 2007, Matthew Woehlke wrote:
> Zack Rusin wrote:
> > Hey, it's a little unfortunate that you decided to dismiss my worries
> > the last time you mentioned this.
>
> You'll have to remind me what worries those were.
>
> > Now all those mentioned H* colorspaces are by definition non-linear
> > transformations of the RGB colorspace. So they, again by definition,
> > lose precision on conversions.
>
> But in 64-bit floating point math (which KColor uses exclusively), the
> loss is negligible. In fact the test suite *requires* that KColor(
> someQColor ).convert( KColor::Hs? ) gives back the original color (at
> least in 8-bpp) when cast back to a QColor. That is the result must
> QColor::operator== the input. So I fail to see why this is a concern.
>
[snip]

Just in case there is really 'data loss': this should go into the api dox, 
maybe along with an image ;)

Dominik