search

jerluc / wmii

Automatically exported from code.google.com/p/wmii
MIT License
0 stars 0 forks source link

Very odd stacking behavior #148

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. make a stack of a few windows
2. use mod+j to select all the way to the bottom window, then press mod-j
once more
3. nothing will be selected, now open up some more windows, they will stack
*behind* the current stack....to see them you have to close all the windows
in the front stack...

What version of the product are you using (wmii -v)? On what operating
system?
wmii-hg2536

Original issue reported on code.google.com by adkilgore on 25 Oct 2009 at 2:56

GoogleCodeExporter commented 9 years ago 
This also happens when you walk off the top of the stack, instead of jumping to 
the
bottom, you can create as many windows in this behind stack as you want, and 
you can
move them side to side behind the current stack, vertical column dividers are 
visible
on top of the front stack

Original comment by adkilgore on 25 Oct 2009 at 3:00

GoogleCodeExporter commented 9 years ago 
I have been experimenting around, when i use the "back" managed layer....it 
seems to
be actually behind the statusbar, (the statusbar covers up the bottoms of the
windows) it happens with stack, max and default modes

Original comment by adkilgore on 25 Oct 2009 at 3:57

GoogleCodeExporter commented 9 years ago 
Additionally, this does not seem to occur if you have two screens

Original comment by adkilgore on 25 Oct 2009 at 7:38

GoogleCodeExporter commented 9 years ago 
I was not sure why my original bug report said hg2536......for some reason...I 
was
still getting 2536 with wmii -v....I freshly downloaded the tip and now get 
hg2574
and this issue isnt happening anymore.....how odd...i guess this report is 
invalid

Original comment by adkilgore on 26 Oct 2009 at 3:37

GoogleCodeExporter commented 9 years ago 
I think I spoke too soon, it is happening to me again, it only appears to 
happen when
I start X with 2 monitors plugged in, but have not configured/added the second 
screen
via xrandr (so the same display is shown on both monitors)

Original comment by adkilgore on 8 Dec 2009 at 8:22

GoogleCodeExporter commented 9 years ago 
wmii-hg2594, ©2009 Kris Maglione

Original comment by adkilgore on 8 Dec 2009 at 8:23

GoogleCodeExporter commented 9 years ago 
Works for me.

Original comment by maglion...@gmail.com on 30 May 2010 at 7:48

GoogleCodeExporter commented 9 years ago 
This still happens for me,  i just plugged in my second monitor, but did not
configure Xorg for dual monitors or configure xrandr, so the display is cloned, 
and i
can walk off the top and bottom of stacks when moving selection around

Is there something I can do to help reproduce and/or diagnose the issue?

Original comment by adkilgore on 30 May 2010 at 8:06

GoogleCodeExporter commented 9 years ago 
Ok, I think I understand the problem now that you describe it that way. It 
suggests
that your configuration gives you two Xinerama screens, one on top of the other,
which happens to be a legal configuration. If that's the case, this isn't a bug 
at
all, but what I'd deem the expected behavior.

Can you post the output of xrandr -q?

Original comment by maglion...@gmail.com on 30 May 2010 at 9:46

GoogleCodeExporter commented 9 years ago 
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096
VGA1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 312mm x 
234mm
   1600x1200      65.0     65.5     60.0  
   1280x1024      75.0  
   1152x864       75.0  
   1024x768       75.1     75.0     70.1     60.0* 
   832x624        74.6  
   800x600        75.0     60.3  
   640x480        75.0     60.0     59.9  
   720x400        70.1  
LVDS1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 286mm x 
214mm
   1024x768       60.0*+   85.0     75.0     70.1     60.0*    50.0  
   832x624        74.6  
   800x600        85.1     72.2     75.0     60.3     56.2  
   640x480        85.0     72.8     75.0     60.0     59.9  
   720x400        85.0  
   640x400        85.1  
   640x350        85.1  
DVI1 disconnected (normal left inverted right x axis y axis)

Original comment by adkilgore on 30 May 2010 at 10:45

GoogleCodeExporter commented 9 years ago 
Yep, that's what I expected. I suppose I could ignore screens that were the 
exact
same size as other screens, maybe even screens that are supersets of other 
screens.
I'll have to think about it. I can't think of any advantage to the current 
behavior.

Original comment by maglion...@gmail.com on 30 May 2010 at 10:59

GoogleCodeExporter commented 9 years ago

Original comment by sun...@gmail.com on 22 Feb 2011 at 9:51

GoogleCodeExporter commented 9 years ago

Original comment by sun...@gmail.com on 22 Feb 2011 at 10:02

GoogleCodeExporter commented 9 years ago 
I cannot reproduce the issue on a single display with wmii-hg2807.

Original comment by sun...@gmail.com on 21 Sep 2011 at 12:31

GoogleCodeExporter commented 9 years ago 
While this probably still occurs with the default X11 autoconfiguration when 
you have two monitors plugged in. It seems that this report was invalid anyway 
because apparently it isn't actually a bug, and isnt an issue if you properly 
configure Xorg, so it can probably be closed as invalid.

Original comment by adkilgore on 21 Sep 2011 at 12:44

GoogleCodeExporter commented 9 years ago 
Closing per reporter's request.

Original comment by sun...@gmail.com on 21 Sep 2011 at 5:13