[RFC PATCH] damageproto: Explicitly document Damage lifetimes
keithp at keithp.com
Thu Mar 29 09:54:47 PDT 2012
On Thu, 29 Mar 2012 12:02:28 -0400, Adam Jackson <ajax at redhat.com> wrote:
> One possibility would be to have a 1.2 version of the protocol that
> simply doesn't generate BadDamage in any event; or, that tracks client
> timestamps and suppresses BadDamage if the drawable has been destroyed
> since the last Damage request; or, that generates DamageDestroyed events
> as well.
XIDs get reused, so you might end up talking about an unexpected damage
object, which means we need the client to be able to know the damage
lifetime. Either a damage destroyed event, a pixmap destroyed event or
having the damage live until explicitly destroyed would all work.
keith.packard at intel.com
More information about the xorg-devel