From 34429d16d319ef2709c22a5c22f45d0e82c78b20 Mon Sep 17 00:00:00 2001 From: Peter Hutterer Date: Sun, 8 Jun 2008 23:08:34 +0930 Subject: [PATCH] xnest: call miDCInitialize rather than miPointerInitialize. This unfortunately gives us a lots of artefacts, so cursor rendering cannot be assumed complete. But it's better than crashing. --- hw/xnest/Screen.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/hw/xnest/Screen.c b/hw/xnest/Screen.c index 61a325f3c..11c180bbb 100644 --- a/hw/xnest/Screen.c +++ b/hw/xnest/Screen.c @@ -305,8 +305,7 @@ xnestOpenScreen(int index, ScreenPtr pScreen, int argc, char *argv[]) pScreen->blockData = NULL; pScreen->wakeupData = NULL; - miPointerInitialize (pScreen, &xnestPointerSpriteFuncs, - &xnestPointerCursorFuncs, True); + miDCInitialize (pScreen, &xnestPointerCursorFuncs); pScreen->mmWidth = xnestWidth * DisplayWidthMM(xnestDisplay, DefaultScreen(xnestDisplay)) /