On Wed, 7 Oct 2009 07:54:51 -0400
Okan Demirmen wrote:
>
> the below changes the current behaviour of fullscreen, now adding
> a border.
>
> of course, if we did this, it would match other tiling wm's, all
> of which i know do have a border, fullscreened or not.
>
If this means the `maximize'
Owain Ainsworth wrote:
> I can't reproduce this here, anymore details?
I think I have found a way to trigger this bug reliably: Try to resize
the window with the mouse to the size it would have if it was maximized
(screen resolution minus gaps) and then press CM-f. Using this method I
can now repr
Okan Demirmen wrote:
> i haven't experienced this (yet) - does this still occur if you simply
> backout the change?
No, no problem at all with revision 1.64 of client.c.
--
Simon Nicolussi,
http://homepage.uibk.ac.at/~csag9583/
On Fri 2009.10.02 at 00:32 +0159, Simon Nicolussi wrote:
> Hello,
>
> as a consequence to the last change to cwm(1) no borders are being drawn
> for maximized windows. This is fine as long as there's no gap defined in
> the cwmrc(5), otherwise the borders between window and gaps are missing.
> Is
On Fri, Oct 02, 2009 at 12:32:42AM +0159, Simon Nicolussi wrote:
> Hello,
>
> as a consequence to the last change to cwm(1) no borders are being drawn
> for maximized windows. This is fine as long as there's no gap defined in
> the cwmrc(5), otherwise the borders between window and gaps are missin
Hello,
as a consequence to the last change to cwm(1) no borders are being drawn
for maximized windows. This is fine as long as there's no gap defined in
the cwmrc(5), otherwise the borders between window and gaps are missing.
Is this behaviour intended?
There's another strange problem I experienc
