Xfwm error handler will cover all errors itself, there is no
necessity to use error traps for client.

GDK X error traps were changed in GDK 3 so using these traps
caused unwanted SIGTRAPs within GDK X error handler.

Bug: 13607

If XPresentPixmap() fails, we would disable Present rather that waiting
for a notification that will never arrive.

But that relies on the actual window to be reported in the XError, which
is not necessarily the case.

Disable Xpresent for all screens as we are not sure we can tell which
one from the resource id.

Błażej Szczygieł authored 7 years ago and Olivier Fourdan committed 7 years ago

Bug: 13613

Since commit 7115d1b4, we can't disable second (broken) vblank waiting
code.

glXSwapBuffers() already waits for v-blank (if enabled in driver), so
any other "synthetic" waiting for v-blank can reduce performance
(de-sync) without actual benefit.

This patch removes old code to prevent waiting for vblank twice.

Bug: 13608

Commit 58955779 (Use ximerama indices for _NET_WM_FULLSCREEN_MONITORS)
introduced a regression because the monitor index was wrongly compared
against the total number of monitors, which would falsely assume that
the Xrandr query failed whereas it actually worked.

Fix the false comparison and also use the screen size as fallback values
in case the Xrandr really failed so that we don't end up using random
uninitialized values.

Prefer Present over GLX if both are available, and remove the
environment variable "XFWM4_USE_PRESENT".

Eventually, we'd rather use a command line option instead (TODO).

This is a leftover of the old (broken) vblank code.

Otherwise the current WM window might have vanished and we wouldn't
know.

Bug: 9351

_NET_WM_FULLSCREEN_MONITORS uses Xinerama indices for multi-monitor
fullscreen, but xfwm4 uses gdk indices which may differ.

As a result, depending on the actual layout and which monitor is marked
as primary, a fullscreen window could be placed on the wrong outputs.

Fetch the Xinerama list and use the monitor size from there instead of
relying on gdk monitor indices for _NET_WM_FULLSCREEN_MONITORS

Bug: 12534

This reverts commit 0dfb5540.

Bug: 13454

We would use the first monitor by default, but we'd rather use the
primary monitor.

Signed-off-by: Olivier Fourdan <fourdan@xfce.org>

NET_WM_STATE_FOCUS is set by the WM itself, it's not an unknown
property.

Bug: 13344

If a window is unmapped while the user is moving or resizing it, we
would cancel the move but swallow the event, which would leave the
window frame on screen as the main event handle would not get the
unmap notify.

Mark the client as gone when detected in the move/resize event loop,
let the event get through to the main event handler that will free the
client and shortcut the move/resize operation if the client is marked
as gone.

The panel is a dock window, and may appear differently as it is not
focused by default by the window manager.

Set the NET_WM_STATE_FOCUSED property on windows of type dock or
spashscreen so that they don't get the state GTK_STATE_FLAG_BACKDROP set
by default.

Signed-off-by: Olivier Fourdan <fourdan@xfce.org>

Bug: 13257

If for some reason XPresentPixmap() fails, we might end up waiting
forever for a present complete notification that will never arrive.

Check for possible errors after XPresentPixmap() and disable XPresent in
case of error.

Signed-off-by: Olivier Fourdan <fourdan@xfce.org>

Add an API to retrieve the screen from the output window.

Signed-off-by: Olivier Fourdan <fourdan@xfce.org>

Signed-off-by: Olivier Fourdan <fourdan@xfce.org>