Bug 3717 - Empty Dock Interferes with Move-/ResizeToEdge Operations
Status: RESOLVED FIXED
Alias: None
Product: Openbox
Classification: Unclassified
Component: general
Version: 3.4.7.2
Hardware: PC Linux
: P3 normal
Assignee: Dana Jansens
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2008-07-14 00:50 EDT by Clay Barnes
Modified: 2009-12-17 10:26:25 EST
0 users

See Also:


Description Clay Barnes 2008-07-14 00:50:14 EDT 
When a window is opened in the SE corner (e.x. 'xterm -geometry -0-0 &') moving west by edge first bumps the window only a pixel, then it moves normally.  Moving it back to the east by edge or resizing it to east by edge also has the mysterious extra stop a pixel from the east edge of the screen.  This same behavior appears in the N-S direction, as well.

Windows starting at any location will encounter this invisible one-pixel stop, as long as they are moving south or east along the east or south edge, respectively.
Comment 1 Clay Barnes 2008-07-14 00:55:16 EDT 
I have discovered that the source of the problem is the dock, which is taking up an invisible 1x1 pixel space in the SE corner.  When empty (as is the case for those of us who don't use it), the dock should not affect window moves/resizes.

For now, the hack of making the dock 'floating' (instead of on an edge or in a corner) seems to avoid the problem for me.
Comment 2 Mikachu 2008-07-14 03:32:07 EDT 
This doesn't seem to happen for me. Are you sure you're using 3.4.7.2 and that you don't have some small window open near that area that gets detected as an edge perhaps? Ie please try it with a completely empty X session. (no hurry, i'm leaving for a few weeks later today :).
Comment 3 Mikachu 2008-07-14 03:32:38 EDT 
Doh, somehow I didn't see the second comment before replying.
Comment 4 Dana Jansens 2009-12-17 10:26:25 EST 
Thanks for the bug report.  This is fixed in commit d3347e8be3753b7a466353aece04a25992018c9a