Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucsd!ames!hc!lll-winken!arisia!sgi!shinobu!odin!fudge!karlton
From: karlton@fudge.sgi.com (Phil Karlton)
Newsgroups: comp.windows.x
Subject: Re: Awm infinite loop problem revisited
Message-ID: <162@odin.SGI.COM>
Date: 23 Jun 89 19:02:11 GMT
References: <3512@ncar.ucar.edu>
Sender: news@odin.SGI.COM
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 22

In article <3512@ncar.ucar.edu> corbet@stout.ucar.edu (Jonathan Corbet) writes:
>Now I have a couple of different questions.  (1) Is the passive grab
>mechanism really working the way I think it is, and is that the way it
>is supposed to work, and (2) any ideas for how to fix this problem?  I
>am not sure why awm busy waits for the release event, but given that
>it does, my feeling is that awm should just do an active grab on the
>pointer to be sure that it gets that release event.  Comments?

(1) Yes and yes.

On page 381 of the Digital Press "X Window System" book it says (under the
description for UngrabPointer)

    An UngrabPointer request is performed automatically if the event
    window or confine-to window for an active pointer grab becomes not
    viewable or ...

(2) One thing awm could be doing is to grab the button syncronously, and
then "convert" the pointer grab to be asyncronous and relative to the root 
window by doing an appropriate GrabPointer call.

PK