Adam Jackson <[email protected]> writes: > Well, no, but it could never matter. The per-screen reports are already > clipped to their respective borderClips (which, as noted, are clipped to > their containing root), and then I'm unioning them all together on > screen 0's DamagePtr. The union of per-root-window borderClips can't > exceed the Xinerama view of the border clip by definition.
Oh, so screen 0 contains all of the damage. Do internal Damage users handle this OK? Or are you reporting out per-physical-screen damage to them and only tracking this union damage for applications? > Doing it in Subtract seems both much simpler and much saner than trying > to wrap configuraton changes, yeah. Cool. Retains the current (slightly mystic) semantics, which always seems safest. -- [email protected]
pgp4pUPJ51qa9.pgp
Description: PGP signature
_______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
