173 translated messages.

Transifex (https://www.transifex.com/xfce/public/).

173 translated messages.

Transifex (https://www.transifex.com/xfce/public/).

173 translated messages.

Transifex (https://www.transifex.com/xfce/public/).

173 translated messages.

Transifex (https://www.transifex.com/xfce/public/).

173 translated messages.

Transifex (https://www.transifex.com/xfce/public/).

171 translated messages, 2 untranslated messages.

Transifex (https://www.transifex.com/xfce/public/).

xfwm4 would send a synthetic configure event while resizing the client
window, which is not what the ICCCM states.

Fix this by sending the synthetic configure event only when necessary,
as per the ICCCM specification.

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

Avoid setting the same flag twice in a row, we already set the
CFG_REQUEST just a few line above.

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

Some client do not process events on their temporary windows, causing
the client unresponsive dialog to show up.

Avoid pinging the client on focus in, even though this is clearly a
client bug.

This reverts commit 637d70b2.

173 translated messages.

Transifex (https://www.transifex.com/xfce/public/).

173 translated messages.

Transifex (https://www.transifex.com/xfce/public/).

170 translated messages, 3 untranslated messages.

Transifex (https://www.transifex.com/xfce/public/).

164 translated messages, 9 untranslated messages.

Transifex (https://www.transifex.com/xfce/public/).

124 translated messages, 49 untranslated messages.

Transifex (https://www.transifex.com/xfce/public/).

170 translated messages, 3 untranslated messages.

Transifex (https://www.transifex.com/xfce/public/).

171 translated messages, 2 untranslated messages.

Transifex (https://www.transifex.com/xfce/public/).

173 translated messages.

Transifex (https://www.transifex.com/xfce/public/).

96 translated messages, 77 untranslated messages.

Transifex (https://www.transifex.com/xfce/public/).

93 translated messages, 80 untranslated messages.

Transifex (https://www.transifex.com/xfce/public/).

To make sure that they are still alive and detect hung clients.

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

When xfwm4 needs to kill an unresponsive client, it will use the its PID
is known.

However, the _NET_WM_PID as defined in the extended window manager hint
mechanism is unreliable when the client runs within a sandbox, as it is
the client itself who sets that property using its own view of the PID.

The Xserver can provide a more accurate value of the client PID using
the XRes X11 extension, so use that protocol if available.

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

The X-Resource extension client library (XRes) allows a client to query
the Xserver for various resources associated with an X11 client,
including its PID.

Add (optional) support for XRes in xfwm4 and use it for getting the
client's PID instead of relying on _NET_WM_PID.

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

173 translated messages.

Transifex (https://www.transifex.com/xfce/public/).

173 translated messages.

Transifex (https://www.transifex.com/xfce/public/).

173 translated messages.

Transifex (https://www.transifex.com/xfce/public/).

173 translated messages.

Transifex (https://www.transifex.com/xfce/public/).

173 translated messages.

Transifex (https://www.transifex.com/xfce/public/).

173 translated messages.

Transifex (https://www.transifex.com/xfce/public/).

173 translated messages.

Transifex (https://www.transifex.com/xfce/public/).

173 translated messages.

Transifex (https://www.transifex.com/xfce/public/).

171 translated messages, 2 untranslated messages.

Transifex (https://www.transifex.com/xfce/public/).

87 translated messages, 86 untranslated messages.

Transifex (https://www.transifex.com/xfce/public/).

173 translated messages.

Transifex (https://www.transifex.com/xfce/public/).

It's easier on the eyes...

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

Bug: 16713

If one of the required X11 extension is not available, the composiutor
cannot be used.

Yet xfwm4 would still try to enable the compositor for each screen,
which would not work and prevent xfwm4 from starting.

If we can't use the compositor, well, we'd better not use it...

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

Clicking outside the tab-win would cancel the selection, make sure to
revert to the original first window of the list in that case, it feels
more natural and predictible.

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

Bug: 16713

Without XRender, the mask would be misrendered and completely
transparent.

As a result, the entire pixmap would become totally transparent and all
window decorations become invisible.

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

Bug: 16708

With Xi2, the clients needs to reset the valuators (for mouse wheel)
themselves, usually on focus events.

Qt instead does that on EnterNotify, but ignores the EnterNotify events
resulting from grabs first. This is a bug in Qt as that prevents the
valuators to be reset if the pointer enters the window while grabbed.

Precisely, xfwm4 would issue a pointer grab while cycling to prevent
from random button events, and would only ungrab after the client window
is raised and focused.

While this is a bug in Qt, we can still work around the issue in xfwm4
by not issuing a pointer grab and simply abort the window cycling when a
click occurs outside of the alt-tab window.

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