mplayer moves 1 step right and 1 step down

If I return mplayer from fullscreen the floating window moves 1 step right and 1 step down. Didn't measure how many pixels it moves. Any idea?

On Fri, Jun 22, 2012 at 4:29 PM, Carsten Mattner < carstenmattner@googlemail.com> wrote:
If I return mplayer from fullscreen the floating window moves 1 step right and 1 step down. Didn't measure how many pixels it moves.
Any idea?
Known, difficult to fix. http://code.google.com/p/xmonad/issues/detail?id=431 -- brandon s allbery allbery.b@gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms

On Fri, Jun 22, 2012 at 11:07 PM, Brandon Allbery
On Fri, Jun 22, 2012 at 4:29 PM, Carsten Mattner
wrote: If I return mplayer from fullscreen the floating window moves 1 step right and 1 step down. Didn't measure how many pixels it moves.
Any idea?
Known, difficult to fix. http://code.google.com/p/xmonad/issues/detail?id=431
Does it happen with any other applications? Sounds like changing MPlayer's fullscreen mode wouldn't make a difference. What's the difficulty?

On Fri, Jun 22, 2012 at 5:21 PM, Carsten Mattner < carstenmattner@googlemail.com> wrote:
On Fri, Jun 22, 2012 at 11:07 PM, Brandon Allbery
wrote: On Fri, Jun 22, 2012 at 4:29 PM, Carsten Mattner
wrote: If I return mplayer from fullscreen the floating window moves 1 step right and 1 step down. Didn't measure how many pixels it moves.
Known, difficult to fix. http://code.google.com/p/xmonad/issues/detail?id=431
Does it happen with any other applications? Sounds like changing MPlayer's fullscreen mode wouldn't make a difference.
What's the difficulty?
It's not related to mplayer at all, but to the way borders interact with floating windows and inappropriately relying on the saved window position. In short, when the position of a floating window is (re)computed, it gets shifted by the border width. (It's more complicated than this, but that's the gist. The actual details involve the inner workings of XMonad.Operations.windows.) -- brandon s allbery allbery.b@gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms

On Fri, Jun 22, 2012 at 11:30 PM, Brandon Allbery
On Fri, Jun 22, 2012 at 5:21 PM, Carsten Mattner
wrote: On Fri, Jun 22, 2012 at 11:07 PM, Brandon Allbery
wrote: On Fri, Jun 22, 2012 at 4:29 PM, Carsten Mattner
wrote: If I return mplayer from fullscreen the floating window moves 1 step right and 1 step down. Didn't measure how many pixels it moves.
Known, difficult to fix. http://code.google.com/p/xmonad/issues/detail?id=431
Does it happen with any other applications? Sounds like changing MPlayer's fullscreen mode wouldn't make a difference.
What's the difficulty?
It's not related to mplayer at all, but to the way borders interact with floating windows and inappropriately relying on the saved window position. In short, when the position of a floating window is (re)computed, it gets shifted by the border width. (It's more complicated than this, but that's the gist. The actual details involve the inner workings of XMonad.Operations.windows.)
OK. I'll see if I can add a rule to set MPlayer's borderWidth to 0. Maybe that could work around the issue. The list of applications I fullscreen and un-fullscreen is short.

At a guess, it's moving down and to the right by the size of your
borderWidth because some piece of software in the stack forgot that X
borders existed. Try setting your borderWidth to something big like 30
and you'll know if this is true. If only mplayer is exhibiting this
behavior, it is likely mplayer that's forgotten; otherwise, check if
you have a compositing manager running or if xmonad itself is doing
some math wrong somewhere.
~d
Quoting Carsten Mattner
If I return mplayer from fullscreen the floating window moves 1 step right and 1 step down. Didn't measure how many pixels it moves.
Any idea?
_______________________________________________ xmonad mailing list xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad

On Fri, Jun 22, 2012 at 6:19 PM,
At a guess, it's moving down and to the right by the size of your borderWidth because some piece of software in the stack forgot that X borders existed. Try setting your borderWidth to something big like 30 and you'll know if this is true. If only mplayer is exhibiting this behavior, it is likely mplayer that's forgotten; otherwise, check if you have a compositing manager running or if xmonad itself is doing some math wrong somewhere.
xcompmgr at least doesn't figure borders into things, so it makes the problem worse; but the real problem is as stated in the bug I pointed to earlier. -- brandon s allbery allbery.b@gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms

On Sat, Jun 23, 2012 at 12:44 AM, Brandon Allbery
On Fri, Jun 22, 2012 at 6:19 PM,
wrote: At a guess, it's moving down and to the right by the size of your borderWidth because some piece of software in the stack forgot that X borders existed. Try setting your borderWidth to something big like 30 and you'll know if this is true. If only mplayer is exhibiting this behavior, it is likely mplayer that's forgotten; otherwise, check if you have a compositing manager running or if xmonad itself is doing some math wrong somewhere.
xcompmgr at least doesn't figure borders into things, so it makes the problem worse; but the real problem is as stated in the bug I pointed to earlier.
I saw a similar window move and resize bugfix applied recently and so want to raise this issue again because it's my only functionality gripe with xmonad. Has there been any insight into this in the meantime?
participants (4)
-
Brandon Allbery
-
Carsten Mattner
-
Carsten Mattner
-
wagnerdm@seas.upenn.edu