Re: [dev] [dwm] floating window if fullscreen

[Nick]

Quoth TJ Robotham:
> Basically, when a client is first created dwm checks to see if its dimensions
> are the same as that of the monitor it's on. If so then the window is set to
> floating.  This logic appears after applying any rules, a rule explicitly
> setting the window to be non-floating will be overriden by this behaviour.
> (I'm presuming that this is in order to respect fullscreen programs even when
> in a different layout.) If you have no use for this, then you can always
> remove it from your version (look in the function manage). 

Thanks a lot for the explanation TJ.

I hadn't quite realised how readable the dwm source is :-)

As I mostly use monocle layout (I'm using a netbook), this behaviour 
isn't ideal for me. Attached is a patch removing that functionality, 
in case anyone else finds it useful.

Nick

diff -r 072c62ed10f2 dwm.c
--- a/dwm.c     Fri Jan 07 16:05:22 2011 +0000
+++ b/dwm.c     Tue Jan 25 01:47:36 2011 +0000
@@ -1102,13 +1102,6 @@
        c->w = c->oldw = wa->width;
        c->h = c->oldh = wa->height;
        c->oldbw = wa->border_width;
-       if(c->w == c->mon->mw && c->h == c->mon->mh) {
-               c->isfloating = True;
-               c->x = c->mon->mx;
-               c->y = c->mon->my;
-               c->bw = 0;
-       }
-       else {
                if(c->x + WIDTH(c) > c->mon->mx + c->mon->mw)
                        c->x = c->mon->mx + c->mon->mw - WIDTH(c);
                if(c->y + HEIGHT(c) > c->mon->my + c->mon->mh)
@@ -1118,7 +1111,6 @@
                c->y = MAX(c->y, ((c->mon->by == 0) && (c->x + (c->w / 2) >= 
c->mon->wx)
                           && (c->x + (c->w / 2) < c->mon->wx + c->mon->ww)) ? 
bh : c->mon->my);
                c->bw = borderpx;
-       }
        wc.border_width = c->bw;
        XConfigureWindow(dpy, w, CWBorderWidth, &wc);
        XSetWindowBorder(dpy, w, dc.norm[ColBorder]);

pgpHNqROJ8QFY.pgp
Description: PGP signature