Re: move/resize handling again

[Dominik Vogt <dominik vogt gmx de>]

On Thu, Nov 14, 2002 at 09:40:50PM +0100, Matthias Clasen wrote:
> As promised, I tried to rewrite Section 7.7 to avoid direct reference to
> the C API. I also tried to avoid the confusion that about combined move
> and resize that started this thread. I also fixed the last listitem to
> refer to the "initial window's size" instead of the "initial window's
> width". I ended up reshuffling some listitems in order to introduce the
> term "reference point" before using it.
> For ease of reviewing, I'll attach a stripped down HTML version of the
> rewrite. I you agree that this version is clearer, I'll commit it.
> Otherwise I can try for a more limited fixup of that section.

The description looks good.  I am a bit unhappy that it seems to
suggest it is a good idea to change the win_gravity often.  The
ICCCM says that the "last" win_gravity is used, but this suffers
from the same problem as with the size inc hints we discussed a
while ago.  The WM only gets a message that is has changed, but
has to look up the value itself.  The hint can already have
changed again when the WM gets around looking it up.  E.g.

  - set NW gravity
  - moveresize to 100x100+0+0
  - set SE gravity
  - resize to 50x50

may be read by the WM as

  - set SE gravity
  - moveresize to 100x100+0+0
  - set SE gravity
  - resize to 50x50

P.S.:  is the § character universally available?

Bye

Dominik ^_^  ^_^