Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!boulder!stan!garya
From: garya@stan.com (Gary Aitken)
Newsgroups: comp.windows.x
Subject: Re: SubstructureRedirect & server out of sync bug
Message-ID: <530@stan.stan.UUCP>
Date: 3 Mar 89 17:35:12 GMT
Organization: Solbourne Computer Inc., Longmont, Co.
Lines: 22

>    The ICCCM states that you'll get a ConfigureNotify event (even
>    if the WM decides not to move you) from a correctly implemented WM.  If you
>    want the "sync", wait for the event.  I don't see that you need the
>    complexity you suggest.

Consider a toolkit which needs to warp the pointer for some reason.
An example would be when input objects are "chained" together;
hitting <CR> on one entry may imply warping the pointer into the next
one to activate input (yes, there are other ways to change the focus...).

In any case, the toolkit knows nothing of what the application has been
doing.  In particular, it does not know if the application has moved some
arbitrary ancestor of the destination window for the warp.  As a
consequence, the toolkit does not know if anything has happened at all,
so it doesn't know whether to wait for the ConfigureNotify or not; and
it has no idea of which ancestor it should look for it on.

An example is a dialog box which is reparented or moved in a context
sensitive manner.

Gary Aitken
ncar!boulder!stan!garya