Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!mit-eddie!bloom-beacon!SUMEX-AIM.STANFORD.EDU!brock From: brock@SUMEX-AIM.STANFORD.EDU (Kevin Brock) Newsgroups: comp.windows.x Subject: Re: problems with xlock Message-ID: Date: 1 Aug 90 16:09:14 GMT Sender: daemon@athena.mit.edu (Mr Background) Organization: The Internet Lines: 19 I've seen the same problem before, but not with xlock. XGrabPointer uses the GrabPointer protocol, which expects to be sent an event mask for the window which is a SETofPOINTEREVENT. The problem is that SETofPOINTEREVENT is an event mask in which certain bits ( 0xffff8003, in fact) *must* be set to zero. The problem arises when the application doesn't check the event mask of the window on which it calls XGrabPointer. In the HP widgets VPanedWindow, for instance, XGrabPointer is called with XtBuildEventMask(widget) for the event mask value, and it doesn't perform any checks on the event mask. In that particular case I've *never* seen it work without a patch, but it sounds like what's happening in xlock is just a variation on a theme. ------------------------------- Kevin Brock brock@sumex-aim.stanford.edu -------