On 11.04.2011 19:12, Keith Packard wrote:
You want to just invoke damageReportDamage directly so that you use
the right damage object, rather than assuming that it is the first
one on the drawable list.
Right, my patch worked rather by accident than by solid code --
apparently my understanding
Instead of using the proper DamageDamageRegion for reporting the
first (virtual) damage in ProcDamageCreate that covers the borderClip
of the drawable window, use a new function DamageInitialReport that
uses damageReportDamage to do the work. This avoids sending all other
damage listeners a full
