Teika Kazura <[email protected]> writes: > Jeremy asks: >> What determines the order by which windows are taken up by sawfish? > > Rule lacks, and that's the very problem. Furthermore, matcher sets > rules for one by one window. But when maximization is involved, then > first it should set "avoided" property for all windows, and > maximization have to succeed that. I don't know the case of > window-history, but I guess it's similar to matcher.
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). -- Jeremy Hankins <[email protected]>
