compiz - Feb 2007 - Horizontally maximized window on last viewport

Hi, 

I posted this on the forum as well, but there were no responses to it. I
now posting it here just in case anybody cares.

Anyway, Compiz is a very nice program. Thanks for all the effort you put
into making it.

I am using the latest git version of compiz and it really works great
for being an "unstable" version. 

Anyway, I noticed the following strange behavior and was wondering if
anybody else experince the same: 

When I have a window maximized horizontally on the last viewport (4) and
try to switch to that window (using either switcher or scale) from the
first viewport (1), the cube rotates to the proper viewport (4) but the
window is moved to the first viewport (1). Shocked

If I then swap to the first viewport (1) again to see the horizontally
maximized window and then toggle the horizontally maximized state, the
window moves back to some other viewport (I have not examined if there
is a pattern to this). 

I am using gentoo and a slightly patched version of libwnck 2.16.2 (from
the xeffects overlay) and have not tried with any other version of
libwmnck as I was not sure libwnck was to blame. 

Anyways, the surprising behavior of the escaping window only occurs when
the horizontally maximized window is on viewport 4 and I try to switch
to it from viewport 1. 

Interestingly, I observe the same behavior under beryl regardless of
window decorator (well: for heliodor and emerald at least, I have not
yet tried any KDE related decorator) 

So! Anyone experiencing the same? 

Cheers 

p.s. Oh! btw. when the window is not maximized horizontally (that would
include: vertically, ordinary, and not maximized), the mentioned
behavior is not observed.

On Fri, 2007-02-02 at 12:03 +0100, Jesper Andersen
wrote:
> Hi, 
> 
> I posted this on the forum as well, but there were no responses to it. I
> now posting it here just in case anybody cares.
> 
> Anyway, Compiz is a very nice program. Thanks for all the effort you put
> into making it.
> 
> I am using the latest git version of compiz and it really works great
> for being an "unstable" version. 
> 
> Anyway, I noticed the following strange behavior and was wondering if
> anybody else experince the same: 
> 
> When I have a window maximized horizontally on the last viewport (4) and
> try to switch to that window (using either switcher or scale) from the
> first viewport (1), the cube rotates to the proper viewport (4) but the
> window is moved to the first viewport (1). Shocked
> 
> If I then swap to the first viewport (1) again to see the horizontally
> maximized window and then toggle the horizontally maximized state, the
> window moves back to some other viewport (I have not examined if there
> is a pattern to this). 
> 
> I am using gentoo and a slightly patched version of libwnck 2.16.2 (from
> the xeffects overlay) and have not tried with any other version of
> libwmnck as I was not sure libwnck was to blame. 
> 
> Anyways, the surprising behavior of the escaping window only occurs when
> the horizontally maximized window is on viewport 4 and I try to switch
> to it from viewport 1. 
> 
> Interestingly, I observe the same behavior under beryl regardless of
> window decorator (well: for heliodor and emerald at least, I have not
> yet tried any KDE related decorator) 
> 
> So! Anyone experiencing the same? 
Yes, it was easy to reproduce with your instructions. I've found the
issue causing this behavior and I've pushed out changes that should fix
it.

Thanks,

- David

Forgot to send this to the mailinglist as well.

On Tue, 2007-02-06 at 20:02 -0500, David Reveman wrote: 
> Yes, it was easy to reproduce with your instructions. I've found the
> issue causing this behavior and I've pushed out changes that should
fix
> it.
Indeed! As I often use horizontally (and or vertically) maximized
windows this was often getting in the way.
> Thanks,
I happy to help.

I am also experience two other issues with window sizes. One is for 1)
maximized windows and another is for 2) "overly" maximized windows.

1)
I usually use Evolution (2.8). I usually have the main window maximized.
When I close the main Evolution window (using either File->Close Window
or ctrl-w) and then restart Evolution, the main window comes up
maximized again. This is the behavior I like. However, if I close down
Evolution (either File->Quit or ctrl-q) and then start Evolution again,
the size of the main window is "as if" maximized, but the window is
not
in a "maximized state" (I can move it which I can't with maximized
windows). 
The problem is not that I can move the window, the problem is that
usually the window is a little larger than maximized (or displaced
perhaps) and so appears on the next viewport as well. The problem with
THAT is evident when I switch to the next viewport (where I can now just
see the right edge of the Evolution window) for some other tasks and try
to switch to Evolution using the switcher or scale.
Since Evolution now slightly appears on my current viewport, instead of
switching viewport to where I opened Evolution focus just changes to the
slightly visible Evolution window which is not very convenient.

I am not sure this is a compiz issue as much as it is Evolution not
remembering it's state correctly? However, if I use Metacity, Evolution
seems to remember maximized state correctly. (Of course, Metacity also
does not use large viewports, so the same issue with slightly visible
windows as mentioned above never occurs here)

2)
The last issue is technically an Evince issue. Evince currently (I am
using 0.6.1) has some issues with resizing it's window. Sometimes, when
opening a new window it is much larger than the viewport. The problem is
then that if it is too large, window decorations turn into white stuff
instead and are not restored to their usual appearance until I resize
the Evince window down to something more manageable. I tried increasing
the size of some random window and then the "white decorations stuff"
happened and compiz gave the following message:

~ $ compiz: pixmap 0x3c03327 can't be bound to texture

So I guess it's an issue with texture sizes?

It's mostly Evince acting silly and I usually maximize Evince windows
anyway. Also, Evince remembers it's maximized state correctly in
contrast to Evolution.


I hope the above is useful somehow.

Cheers,
Jesper