Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!amdcad!ames!mailrus!tut.cis.ohio-state.edu!bloom-beacon!SUN.COM!dshr
From: dshr@SUN.COM (David Rosenthal)
Newsgroups: comp.windows.x
Subject: Re: SubstructureRedirect & server out of sync bug
Message-ID: <8903022227.AA00806@devnull.sun.com>
Date: 2 Mar 89 19:16:35 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 21

You are correct that clients which ignore the possibility that their
operations may have been re-directed may not operate correctly.  It
did not turn out to be possible to ensure that a client would be
totally unaware of possible redirection.  Your example is but one
of the cases in which this is true.

The set of operations that may be re-directed and the consequences
of this re-direction are set out in Section 4.2 of the Inter-Client
Communications Conventions Manual.

In particular,  clients that want to move their top-level window
and operate correctly in it will need to select for ConfigureNotify
events,  and change their view of its position only when the
event arrives.  Clients which do operations (such as your example of
WarpPointer) that have global rather than window-local effects have
to be aware of this possibility.

Note that the ICCCM deprecates the whole idea of clients warping the
pointer,  anyway.

	David.