Re: [dwm] Testing layouts

From: Anselm R. Garbe <>
Date: Sun, 12 Aug 2007 13:17:11 +0200

On Sat, Aug 11, 2007 at 08:30:35PM +0200, pancake wrote:
> This fix can be easily done by adding two lines in the prev/nextclient
> function checking if cpt != 0..but this looks ugly to me..maybe dwm
> have to raise the current selected window at top automatically?
> If cpt (or dwm?) fixes this, the monocle patch will not be required
> anymore to fit this. The "problem" is that all the rest of layouts
> require modification to use the 'cpt' concept.

I darkly remember this autoraise would break in floating layout
if you try to reach a small window which is completely covered
by a big/fullscreen window... but am not sure...

> 2) floating and swapping layouts
> About the floating layout I think it's useful, but only when you are
> predisposed to use the mouse. btw, the moveresize patch is not as usable
> as it should.
> These comes again on the toggable dilema. Should a layout can be
> toggable? something like ^floating, so you could put/drop a layout
> with the same keybinding.
> A similar approach would be to implement something like setlayout(NULL)
> but allowing '-1'. To be able to go forward or backward when changing
> between layouts. IMHO it's problematic when you have >2 layouts.

More than 2 layouts are always used better with separate keys, e.g.
Mod1-f for floating, Mod1-t for tiling, Mod1-b for bstack,
Mod1-g for grid...

> 3) {h,v}factor
> After testing it some days I can agree that it's probably not a good
> approach, why not trying with a percentatge instead of a factor?

I'm not sure...


 Anselm R. Garbe >< >< GPG key: 0D73F361
Received on Sun Aug 12 2007 - 13:17:11 UTC

This archive was generated by hypermail 2.2.0 : Sun Jul 13 2008 - 14:49:06 UTC