[MPlayer-users] [BUG] Switching between fs and windows breakage with XV, XMGA and X11.
Jan Knutar
jknutar at nic.fi
Sun Apr 25 05:12:03 CEST 2004
Another reply to myself, yay.
After moving the windowed one, the fullscreen window will have its x,y
coordinates in the exact same place as the windowed one, so, if I for
example, move the window to upper left corner before I press f for
fullscreen, the fullscreen window is correctly positioned.
printf debugging of x11_common.c reveals that for the messed up case,
XmoveResizeWindow() and vo_x11_sizehint() are being called with the
correct 0,0 coordinates (I assume that would be correct, atleast),
exactly the same as in the non-messed up case.
I might be wrong, but it's almost like I get a flash of some sort on my
screen when I switch to fullscreen, like the window would be correctly
positioned for a fraction fo a second, before it gets moved to wrong
place... Is metacity moving it? Wouldn't mplayer be notified of such a
move, and that show up in -v from vo_xv? I hate X now :-(
Hm, here's -v -vo xmga (xmga seems to produce more interesting output in
the terminal than xv) after moving window, then pressing f:
[xmga] x: 296 y: 312 w: 560 h: 240
[xmga] dcx: 296 dcy: 312 dx: 0 dy: 0 dw: 560 dh: 240
*** [vo] Allocating (slices) mp_image_t, 560x240x12bpp YUV planar,
201600 bytes
[xmga] x: 6 y: 20 w: 560 h: 240
[xmga] dcx: 296 dcy: 312 dx: 0 dy: 0 dw: 560 dh: 240
*** [vo] Allocating (slices) mp_image_t, 560x240x12bpp YUV planar,
201600 bytes
*** [vo] Allocating (slices) mp_image_t, 560x240x12bpp YUV planar,
201600 bytes
(movie is playing at this point)
[xmga] x: 6 y: 20 w: 560 h: 240
[xmga] dcx: 300 dcy: 311 dx: 0 dy: 0 dw: 560 dh: 240
(moved the window a little bit)
Calling vo_x11_sizehint(0, 0, 1152, 864, 0)
[x11] NET style stay on top (layer 1). Using state _NET_WM_STATE_ABOVE.
Calling XmoveResizeWindow(mDisplay, vo_window, 0, 0, 1152, 864)
[xmga] x: 294 y: 291 w: 560 h: 240
[xmga] dcx: 294 dcy: 291 dx: 0 dy: 0 dw: 560 dh: 240
[xmga-fs] dcx: 294 dcy: 476 dx: 0 dy: 185 dw: 1152 dh: 494
[xmga] x: 294 y: 291 w: 560 h: 240
[xmga] dcx: 294 dcy: 291 dx: 0 dy: 0 dw: 560 dh: 240
[xmga-fs] dcx: 294 dcy: 476 dx: 0 dy: 185 dw: 1152 dh: 494
[xmga] x: 0 y: 0 w: 1152 h: 864
[xmga] dcx: 0 dcy: 0 dx: 0 dy: 0 dw: 1152 dh: 864
[xmga-fs] dcx: 0 dcy: 185 dx: 0 dy: 185 dw: 1152 dh: 494
[xmga] x: 300 y: 311 w: 1152 h: 864
[xmga] dcx: 300 dcy: 311 dx: 0 dy: 0 dw: 1152 dh: 864
[xmga-fs] dcx: 300 dcy: 496 dx: 0 dy: 185 dw: 1152 dh: 494
(and that whole chunk above after pressing f, nothign else)
As a sidenote, I see these messages from metacity:
Window manager warning: Window 0x5600002 (MPlayer) sets an MWM hint
indicating it isn't resizable, but sets min size 4 x 4 and max size
2147483647 x 2147483647; this doesn't make much sense.
More information about the MPlayer-users
mailing list