Path: utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!helios.ee.lbl.gov!pasteur!ucbvax!decwrl!labrea!rutgers!tut.cis.ohio-state.edu!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: Expose, EnterNotify events
Message-ID: <8901202134.AA02335@EXPIRE.LCS.MIT.EDU>
Date: 20 Jan 89 21:34:27 GMT
References: <2810306070-14946088@Sierra>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 12


    In practice, however, this amounts to a
    defect in the protocol, because it severely constrains the usefulness of
    FocusIn/Out.

True.  Note that Enter/Leave events contain a focus flag, which was supposed
to carry the same information.  And it does, except for unpleasant interactions
with pointer grabs that we didn't realize early enough on.  It is thought that
a reasonable (hopefully upward compatible) design change would be to always
send FocusIn/Out events when windows get/lose the focus (e.g. with a new
detail "Pointer").  I suspect this is on Hania's list at her X Conference
talk ...