[RFC] [PATCH] [xorg/xserver] damage: use DamageExtReport for the initial borderClip damage report

Adam Jackson ajax at nwnk.net
Thu Mar 24 06:41:09 PDT 2011

On Thu, 2011-03-24 at 13:46 +0200, Erkki Seppälä wrote:
> Instead of using the "proper" DamageDamageRegion for reporting the
> first (virtual) damage in ProcDamageCreate that covers the borderClip
> of the drawable window, use DamageExtReport directly. This avoids
> sending all other damage listeners from receiving a full window update
> when a new damage object is created.

There's still one semantic difference between this and the original:
you're not adding the initial region to the Damage.  I'm not completely
sure if that matters in any existing app, but it's probably better to
assume it does.

It looks like damageReportDamage() might do what we want.

- ajax
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://lists.x.org/archives/xorg-devel/attachments/20110324/96b4467a/attachment.pgp>

More information about the xorg-devel mailing list