I said: > One way to go would be to duplicate what the matcher stuff does: > maximization is queued to take place later by setting window properties > like queued-vertical-maximize, which is caught and acted upon later (in > the after-add-window-hook). > > But I don't understand what's going on when sawfish starts up and there > are already windows managed by the server (e.g., on sawfish restart).
Of course, I should be clear: this wouldn't solve Chris's maximization problem, since that has to do with the order of the horizontal and vertical components of maximization. -- Jeremy Hankins <[email protected]>
