From e409fb32b97033718f270a273f29f24c0b562b84 Mon Sep 17 00:00:00 2001 From: Erkki Seppälä Date: Tue, 12 Apr 2011 12:55:56 +0300 Subject: damage: use DamageReportDamage for the initial borderClip damage report MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Instead of using DamageDamageRegion for reporting the first (virtual) damage in ProcDamageCreate that covers the borderClip of the drawable window, use a function DamageReportDamage directly (previously called damageReportDamage). This avoids sending all other damage listeners a full window update when a new damage object is created. As this patch makes DamageReportDamage a public interface, the function has been moved into the part of the file that contains all the other public functions. The function has not been otherwise modified. Signed-off-by: Erkki Seppälä Reviewed-by: Keith Packard Signed-off-by: Keith Packard --- damageext/damageext.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'damageext') diff --git a/damageext/damageext.c b/damageext/damageext.c index 754383d49..02db88a8e 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); + DamageReportDamage(pDamageExt->pDamage, pRegion); } return Success; -- cgit v1.2.3