Am 22.03.2012, 08:55 Uhr, schrieb Kai-Uwe Behrmann <ku.b@gmx.de>:

> Lets hypothetical assume some effort is initiated to bring CM to Qt and
> that happens during Qt 5 life time. The new design says by default all
> content is considered sRGB, which is by itself reasonable. However
> existing applications will initially not know about that changed
> convention.
Errrmmm... how is that please different from opting out of the compositor?
Except that latter does not only hit Qt applications but also *every*  
"legacy" stuff around?

> The conflict is solveable by making the new drawing API incompatible with
> the old one, e.g. requiring a colour space argument.
Or by making user code color correction calls  
(QApplication::setColorSpec(int spec)?) invalidate/override library  
settings?

Cheers,
Thomas
_______________________________________________
kwin mailing list
kwin@kde.org
https://mail.kde.org/mailman/listinfo/kwin