On Wed, 2016-09-14 at 14:01 -0400, Stirling Westrup wrote:
> I'm currently reading through the source for the damage extension in
> damage.c and I noticed that the list of functions that get wrapped
> when a screen gets damage support is not the same as the list of
> functions that get unwrapped wh
I'm currently reading through the source for the damage extension in
damage.c and I noticed that the list of functions that get wrapped when a
screen gets damage support is not the same as the list of functions that
get unwrapped when the screen is closed. That is DamageSetup() wraps these
function
