On Tue, Jul 07, 2009 at 10:30:27PM +0100, Thomas Adam wrote:
> 2009/7/7 Kathryn Andersen <kat_lists@kats...>:
> > On Tue, Jul 07, 2009 at 09:37:11PM +0100, Thomas Adam wrote:
> >> 2009/7/7 Kathryn Andersen <kat_lists@kats...>:
[snip]

> > Here's some more detailed examples...
> >
> > Layout A: Two Columns
> >
> > FvwmRearrange -m
> > 2 Windows: 2 columns (good)
> > 3 Windows: 3 columns (not want)
>
> The trick to this, and *all* of these is to mark windows as ignorable
> by FvwmRearrange.  You can do this by using the following:
>
> * Mark a window as being ignorable by FvwmRearrange.
> * Tile all others.
>
> As in:
>
> DestroyFunc Arrange
> AddToFunc Arrange
> + I ThisWindow (Transient) Break
> + I ThisWindow (!Focused) Focus
> + I Current WindowStyle WindowListSkip
> + I Schedule 250 Module FvwmRearrange -tile -noraise -u -m -mn 2 $0
> + I Current WindowStyle WindowListHit
> + I UpdateStyles
>
> The point here is the WindowListSkip / WindowListHit conditions which
> FvwmRearrange will listen to.  WindowListSkip windows (i,e., those
> with that style set) are ignored by FvwmRearrange.   Those with
> WindowListHit are not.  So armed with that knowledge you should be
> able to approximate your layouts from XMonad.

So that would put two windows in two-column mode and leave all the
others as they are?  Not quite what I want, as far as I can see.
Though I suppose one could also do it by iconifying the remaining
windows...

> To achieve some of your other layouts, what you might want to do is
> set a State (see "man fvwm") property on certain windows, so you're
> then able to condition when/when not to apply WindowList{Skip,Hit}
> rules, for instance.

That seems overly complicated, somehow.

> Note that I have several patches to FvwmRearrange floating around --
> mostly to make it useful for use with "ModuleSynchronous" - but I
> haven't commited it upstream yet, and likely won't given my current
> workload on FVWM as it is for a while.
>
> If this approach still isn't useful to you, I would seriously augment
> FvwmRearrange.  If you're not capable of doing that yourself, make a
> list and I will add it to my todo list; the code for FvwmRearrange is
> not complex.

It's written in C, yes?  My C is a bit rusty, but I suppose I could take
a look.
On the other hand... I've progressed enough on my module that it almost
works, which means I'm tempted to just keep on working on it and not
worry about FvwmRearrange, especially as you are busy.

Thanks for your help. 8-)

Kathryn Andersen
--
_--_|\     | Kathryn Andersen <http://www.katspace.com>
/      \    |
\_.--.*/    | GenFicCrit mailing list <http://www.katspace.com/gen_fic_crit/>
      v     |
------------| Melbourne -> Victoria -> Australia -> Southern Hemisphere
Maranatha!  | -> Earth -> Sol -> Milky Way Galaxy -> Universe