[MPlayer-dev-eng] [PATCH] x11 vo drivers override user settings for window placement
mark at fluxbox.org
Sun Jun 24 22:57:18 CEST 2007
> > First of all, since you're setting the size hint, the only reason to
> > move the window at all is in case there isn't a window manager
> No, the reason for this is to _force_ a certain position of the
> window, overriding the window manager. I proposed this way of
> doing it based on some "standard" i've read at that time about
> forcing the window position (it should be the ICCCM, but i'm not sure)
> > running. While that probably happens more often for a video player
> > than most applications, I'd still wager it's pretty rare. However, you
> > don't have to give up on that case to resolve this. You can just move
> > the window before mapping it.
> That wont work. Most window manager move the window _after_ mapping,
> thus overriding MPlayers prefered position.
I see the problem here. You've confused mplayer with a window manager.
Here are some quotes from that strange document you mentioned, which
can be found at http://tronche.com/gui/x/icccm/sec-4.html .
"To permit window managers to perform their role of mediating the
competing demands for resources such as screen space, the clients
being managed must adhere to certain conventions and must expect the
window managers to do likewise. These conventions are covered here
from the client's point of view."
"Each window manager will implement a particular window management
policy; the choice of an appropriate window management policy for the
user's circumstances is not one for an individual client to make but
will be made by the user or the user's system administrator."
"For example, the claim is often made: "The client I'm writing is
important, and it needs to be on top." Perhaps it is important when it
is being run in earnest, and it should then be run under the control
of a window manager that recognizes "important" windows through some
private protocol and ensures that they are on top. However, imagine,
for example, that the "important" client is being debugged. Then,
ensuring that it is always on top is no longer the appropriate window
management policy, and it should be run under a window manager that
allows other windows (for example, the debugger) to appear on top."
Keep reading on your own.
More information about the MPlayer-dev-eng