[PATCH 1/2] Replace usage of DamageRegionAppend with DamageDamageRegion to fix reportAfter.

[Keith Packard]

On Sat, 30 Oct 2010 18:07:19 +0200, Michel Dänzer <michel at daenzer.net> wrote:

> Right, but as long as there's at least one rendering operation in
> between, at that point EXA will synchronize the pixmap copies according
> to the accumulated pending damage. That's the assumption broken by your
> change.

Eric's patch just catches a few non-rendering paths where post-op damage
would not generate Damage events, as DamageRegionProcessPending would
never have been invoked. For all rendering paths, it changes nothing
(the change in EXA simply calls DamageDamageRegion instead of the
equivalent in-line sequence of DamageRegionAppend followed by
DamageRegionProcessPending).

-- 
keith.packard at intel.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg-devel/attachments/20101030/e76ced1e/attachment.pgp>