[Openicc] XRandR 1.2 and _ICC_PROFILE property.

[Ross Burton]

Graeme,

On Thu, 2008-03-13 at 13:51 +1100, Graeme Gill wrote:
> The logical way of doing this is to instead add an _ICC_PROFILE
> property to the randr output object. To be a full implementation
> there would actually have to be a utility that is monitoring
> RandR events, and tracking the EDID data for each output,
> and keeping a table of monitor make, model and serial number
> vs. icc profile, so that if a user changes the display, the
> correct calibration and ICC profile will automatically
> be switched to the associated output property.
> 
> Color aware applications or graphics toolkits should ideally
> be XRandR 1.2 sensitive, and look to the _ICC_PROFILE property
> of the output object, and use it for regions of the screen
> that any of the outputs CRTCs cover.

This sounds right to me.  I'm glad to see that output properties can be
created by the clients, so writing a trivial library to wrap this should
be easy.

Ross
-- 
Ross Burton                                 mail: ross at burtonini.com
                                          jabber: ross at burtonini.com
                                     www: http://www.burtonini.com./
 PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.freedesktop.org/archives/openicc/attachments/20080314/86ce20c3/attachment.pgp