gtk+ and randr

[Adam Jackson]

On Thu, 2008-07-24 at 13:28 +1000, Graeme Gill wrote:
> Adam Jackson wrote:
> > So basically the upshot is you can't treat EDID fetch as cheap, and thus
> > any information derived from it should not be in APIs expected to be
> > called a lot.  Now as far as I can tell, gtk really just wants the
> > active screen topology, so it can know where the borders of the glass
> > are for placement and where to maximize presentations to.  _That_ we can
> > know cheaply.
> 
> For maintaining color display calibration, an event notifying the
> calibration upload daemon is needed whenever a display is connected.
> It will be looking for the EDID to match it with the appropriate
> calibration and/or ICC profile, so ideally the output EDID property
> should be updated by the server, and a property change event generated,
> which the daemon can monitor.

As has been noted several times now, this is because the code to send
output property change events is flat out unimplemented.

A naïve implementation of same that might even work:

http://people.freedesktop.org/~ajax/patches/randr-deliver-events-dammit.patch

Keith, does this look sane?

- ajax
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://lists.x.org/archives/xorg/attachments/20080729/29dea8f0/attachment.pgp>