Hi, I built one server with and one without the patch:-
--- ./programs/Xserver/hw/xwin/save_windialogs.c 2005-11-14 12:20:44.000000000 +0000 +++ ./programs/Xserver/hw/xwin/windialogs.c 2005-11-14 12:25:22.000000000 +0000 @@ -400,8 +400,9 @@ { g_fCursor = TRUE; ShowCursor (TRUE); + return TRUE; } - return TRUE; + break; case WM_CLOSE: DestroyWindow (g_hDlgExit); @@ -650,8 +651,9 @@ { g_fCursor = TRUE; ShowCursor (TRUE); + return TRUE; } - return TRUE; + break; case WM_COMMAND: switch (LOWORD (wParam)) and so far I've had 0 cursor failures with and 1 failure without it. Both servers running multiwindows with the default hardware cursor. An empirical result, perhaps not yet significant, but ShowCursor(TRUE) vs ShowCursor(FALSE) must be getting out of step somewhere/somehow, and I couldnt see why removing all the software cursor code helped when I hacked it all out, some time ago, in desperation? (The ShowCursor entry in the task menu calls ShowCursor(TRUE) as a restore/remedy when it disappears) see http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winui/winui /windowsuserinterface/resources/cursors/cursorreference/cursorfunctions/show cursor.asp This bug is a slippery customer, only appears once a blue-moon, so I'll keep on trucking and get more stats. Colin Harrison -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/