Dmitry Timoshkov wrote:
"Havoc Pennington" <[EMAIL PROTECTED]> wrote:
Dmitry Timoshkov wrote:
It's OK that a WM constrains windows to be placed inside of its work
area
but still allows to place them into a fullscreen state on request.
How would
you suggest to proper
Dmitry Timoshkov wrote:
It's OK that a WM constrains windows to be placed inside of its work area
but still allows to place them into a fullscreen state on request. How
would
you suggest to properly inform a WM that a window needs to be in a
fullscreen
state? Does metacity ignore ClientMessage
Dmitry Timoshkov wrote:
At this point WM decides to correct position of an invisible application's
window (why?)
In the metacity log, this is in the proper order (the window is mapped,
metacity sets its position, and the window is withdrawn). I would
conclude that this is a race; remember th
Something I think I may have suggested long ago is some sort of "WINE
hints" that WMs could implement; in essence, have calls to the WM that
map to Windows API calls exactly and try to have the same semantics. IOW
implement the windows API in conjunction with the WM.
This is probably the only
Dmitry Timoshkov wrote:
1. Why the WM thinks that it knows better than the app where to place
its window
and insists on moving it to another position? That's not a user related
interaction
related to moving a window using mouse or a keyboard, IMO the WM should
not do
this kind of things behi
Dmitry Timoshkov wrote:
Anyway, few WM bugs can be resolved by appeal to specifications alone...
Ok, let's appeal to the fact that Wine's fullscreen stuff works in KDE and
doesn't in GNOME :-) If you could point out what Wine is doing in wrong way
I'm all ears.
Don't get defensive, everyone i
Dmitry Timoshkov wrote:
An algorithm in Wine which asks a WM to activate fullscreen state for
a window is quite simple: it checks the size of a just resized visible
window and if it's equal or larger than screen size sends an event to
a WM. We are trying to understand at the moment why metacity s
Dmitry Timoshkov wrote:
So, all the checks metacity does for window decorations and window size are
contradicting the spec IMO.
Both the ICCCM and EWMH are specs for "hints" - they have a big "any of
these hints may be ignored" disclaimer attached.
In practice, categorically ignoring (or mis
Look at src/window.c:recalc_window_features() for possible reasons
metacity decided to disable fullscreenability.
In this case it looks pretty clear though - the firefox window isn't
resizable, metacity disables fullscreen in that case unless the window
size is equal to the screen size and the
