Erkki Seppälä e409fb32b9 damage: use DamageReportDamage for the initial borderClip damage report ... 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ä <erkki.seppala@vincit.fi> Reviewed-by: Keith Packard <keithp@keithp.com> Signed-off-by: Keith Packard <keithp@keithp.com>		2011-04-13 18:59:09 -07:00
..
damage.c	damage: use DamageReportDamage for the initial borderClip damage report	2011-04-13 18:59:09 -07:00
damage.h	damage: use DamageReportDamage for the initial borderClip damage report	2011-04-13 18:59:09 -07:00
damagestr.h	unifdef -B -DRENDER to always include RENDER code	2010-04-19 09:26:10 -07:00
Makefile.am	damage: Remove hw/xfree86/ from includes	2011-02-08 12:41:20 -05:00