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.
Signed-off-by: Erkki Seppälä <erkki.sepp...@vincit.fi>
---
damageext/damageext.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/damageext/damageext.c b/damageext/damageext.c
index cfef069..7a0a779 100644
--- a/damageext/damageext.c
+++ b/damageext/damageext.c
@@ -223,7 +223,7 @@ ProcDamageCreate (ClientPtr client)
if (pDrawable->type == DRAWABLE_WINDOW)
{
pRegion = &((WindowPtr) pDrawable)->borderClip;
- DamageDamageRegion(pDrawable, pRegion);
+ DamageExtReport(NULL /* pDamage not used */, pRegion, pDamageExt);
}
return Success;
--
1.7.0.4
_______________________________________________
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel
