From f36153e3ef6b13a87d016caab09cc9be274b0dd5 Mon Sep 17 00:00:00 2001 From: Eric Anholt Date: Thu, 28 Oct 2010 20:46:22 -0700 Subject: Replace usage of DamageRegionAppend with DamageDamageRegion to fix reportAfter. In all these cases, any rendering implied by this damage has already occurred, and we want to get the damage out to the client. Some of the DamageRegionAppend calls were explicitly telling damage to flush the reportAfter damage out, but not all. Bug #30260. Fixes the compiz wallpaper plugin with client damage changed to reportAfter. Signed-off-by: Eric Anholt Reviewed-by: Keith Packard Signed-off-by: Keith Packard --- damageext/damageext.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'damageext') diff --git a/damageext/damageext.c b/damageext/damageext.c index f5265ddfc..4aa0ff3a1 100644 --- a/damageext/damageext.c +++ b/damageext/damageext.c @@ -222,7 +222,7 @@ ProcDamageCreate (ClientPtr client) if (pDrawable->type == DRAWABLE_WINDOW) { pRegion = &((WindowPtr) pDrawable)->borderClip; - DamageRegionAppend(pDrawable, pRegion); + DamageDamageRegion(pDrawable, pRegion); } return Success; @@ -292,7 +292,7 @@ ProcDamageAdd (ClientPtr client) * screen coordinates like damage expects. */ RegionTranslate(pRegion, pDrawable->x, pDrawable->y); - DamageRegionAppend(pDrawable, pRegion); + DamageDamageRegion(pDrawable, pRegion); RegionTranslate(pRegion, -pDrawable->x, -pDrawable->y); return Success; -- cgit v1.2.3