From 961333143e2df3e3f33e8624fc61e79cf3e86cd1 Mon Sep 17 00:00:00 2001
From: Eric Anholt <anholt@freebsd.org>
Date: Thu, 12 Aug 2004 08:45:33 +0000
Subject: Apply a kludge to initialize the composite wrapper before
 DamageSetup. If     not, DamageSetup will wrap some operations first, and the
 cw     initializes during ExtensionInit, so cw comes higher in the wrapping  
   chain. cw going first will result in damage getting confused when the    
 drawables get changed around.

---
 composite/compinit.c | 3 ---
 1 file changed, 3 deletions(-)

(limited to 'composite/compinit.c')

diff --git a/composite/compinit.c b/composite/compinit.c
index f3dc0373e..759c1d3f9 100644
--- a/composite/compinit.c
+++ b/composite/compinit.c
@@ -26,7 +26,6 @@
 #include <config.h>
 #endif
 #include "compint.h"
-#include "cw.h"
 
 int	CompScreenPrivateIndex;
 int	CompWindowPrivateIndex;
@@ -362,8 +361,6 @@ compScreenInit (ScreenPtr pScreen)
     cs->CloseScreen = pScreen->CloseScreen;
     pScreen->CloseScreen = compCloseScreen;
 
-    miInitializeCompositeWrapper(pScreen);
-
     pScreen->devPrivates[CompScreenPrivateIndex].ptr = (pointer) cs;
     return TRUE;
 }
-- 
cgit v1.2.3