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 of the Damage code wasn't deep enough yet. After this post follows a patch that makes use of a now-published function damageReportDamage function instead (under the name DamageReportDamage), calling it directly with the created damage object. _______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
