On 24.03.2011 15:41, Adam Jackson wrote:
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 damageRepor
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 listene
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
