Re: [PATCH] maximize-horizontally/vertically behaviour change + fix

[Teika Kazura <teika lavabit com>]

On Tue, 8 Dec 2009 15:47:50 +0100, Christopher Roy Bratusek wrote:
> Am Tue, 08 Dec 2009 13:55:03 +0900 (JST)
> schrieb Teika Kazura <teika lavabit com>:
>
>> The change is done in commit 6071da, by Jeremy. Let's wait for
>> him. (Well, he seems to be busy. ;)
>
> Hmm... nope, the problem exists for years now, see:
>
> https://bugzilla.gnome.org/show_bug.cgi?id=104591

Oops, sorry Jeremy.

And, sorry Chris. I replied by only skimming, not by understanding
what you said.

Is what you want:
before:
 --
|  |
|A |   ------
|  |  |trayer|
 --    ------

after:
 -----
|     |
|  A  |------
|     |trayer|
 ----- ------

But afterwards, A is fully maximized, right? It's by restart?

I've tried similar case with restart, but your patch doesn't help.
(With matcher, set A 'avoid', and max'ize another window for all
directions. Ok, it avoids A. Now restart, and A is covered.)  It also
contains definition change for horiz/vert max'n, but it's not natural
save bugfix, so can't be adopted. Of course it's good that a
workaround

By the way, do you set 'avoid' property to trayer from rc / config?
Is it saved with history?

If win A and trayer have fixed size, then there's another workaround:
use grow, and save dimension and size, by matcher or window history.

I guess the cause is window-history or matcher.  In general, these two
and the startup procedure is a blackbox, and needs review. I can't say
anything more for sure on this issue now.

Teika (Teika kazura)