RE: Pointer bug in multiwindow mode (native window manager)

[Stef Simoens <stefaan dot simoens at coditel dot net>]

> you can run XWin with -logverbose 3 parameter. This will print some
> debugging information to the logfile which may help figuring out why
> the cursor disappears.
> If you encounter the problem another time, please send me your
> /tmp/XWin.log

I also have the 'dissapearing mouse pointer'-phenomenon. It mostly 
happens after a while.

This is my logoutput (with -logverbose 3):

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 6.7.0.0-9

Contact: cygwin-xfree@cygwin.com

XWin was started with the following command line:

Xwin -broadcast -clipboard -lesspointer -logverbose 3 -screen 0 1024
768 -once

ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - w 1400 h 1050
winInitializeDefaultScreens - Returning
ddxProcessArgument - screen - Found ``W D'' arg
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
winValidateArgs - Returning.
(II) XF86Config is not supported
(II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
winDetectSupportedEngines - Windows NT/2000/XP
winDetectSupportedEngines - DirectDraw installed
winDetectSupportedEngines - DirectDraw4 installed
winDetectSupportedEngines - Returning, supported engines 00000007
winScreenInit - dwWidth: 1024 dwHeight: 768
winSetEngine - Using Shadow DirectDraw NonLocking
winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits 
per pixel
winCreateBoundingWindowWindowed - User w: 1024 h: 768
winCreateBoundingWindowWindowed - Current w: 1024 h: 768
winAdjustForAutoHide - Original WorkArea: 0 0 1020 1400
winAdjustForAutoHide - Adjusted WorkArea: 0 0 1020 1400
winCreateBoundingWindowWindowed - WindowClient w 1024 h 768 r 1024 l 0 b 
768 t 0
winCreateBoundingWindowWindowed -  Returning
winCreatePrimarySurfaceShadowDDNL - Creating primary surface
winCreatePrimarySurfaceShadowDDNL - Created primary surface
winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface
winAllocateFBShadowDDNL - lPitch: 4096
winAllocateFBShadowDDNL - Created shadow pitch: 4096
winAllocateFBShadowDDNL - Created shadow stride: 1024
winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff
winInitVisualsShadowDDNL - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 
bpp 32
winRandRInit ()
winCreateDefColormap - Deferring to fbCreateDefColormap ()
winFinishScreenInitFB - returning
winScreenInit - returning
InitOutput - Returning.
(--) Setting autorepeat to delay=500, rate=31
(--) winConfigKeyboard - Layout: "0000040C" (0000040c)
(--) Using preset keyboard for "French (Standard)" (40c), type "4"
Rules = "xorg" Model = "pc105" Layout = "fr" Variant = "(null)" Options 
= "(null
Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing 
from li
Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, 
removing from
Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, 
removing from
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing 
from li
Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, 
removing from
winPointerWarpCursor - Discarding first warp: 512 384
winBlockHandler - Releasing pmServerStarted
winBlockHandler - pthread_mutex_unlock () returned
winProcEstablishConnection - Hello
winProcEstablishConnection - Xdmcp enabled, waiting to start clipboard 
client un
winProcEstablishConnection - Hello
winProcEstablishConnection - Xdmcp enabled, waiting to start clipboard 
client un
winProcEstablishConnection - Hello
winProcEstablishConnection - Xdmcp enabled, waiting to start clipboard 
client un
winInitClipboard ()
winProcQueryTree - winInitClipboard returned.
winClipboardProc - Hello
DetectUnicodeSupport - Windows NT/2000/XP
winClipboardProc - DISPLAY=127.0.0.1:0.0
winProcEstablishConnection - Hello

(...) a lot of winClipboardWindowProc messages, I don't think they are 
relevant here.

Stef Simoens