169 translated messages.

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

169 translated messages.

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

169 translated messages.

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

169 translated messages.

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

169 translated messages.

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

169 translated messages.

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

169 translated messages.

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

169 translated messages.

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

Bug: 14323

On unmap/destroy, the damage may already be destroyed along with the
attached resource, make sure we catch those errors so it doesn't bother
gtk+.

This adds:
  myDisplayErrorTrapPush()
  myDisplayErrorTrapPop()
  myDisplayErrorTrapPopIgnored()
  myDisplayBeep()
  myDisplayGetKeymap()

Se we don't have to check for gtk+ version all over the place.

167 translated messages, 2 untranslated messages.

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

That would prevent building with --enable-debug=full

Make traces more consistent.

Andre Miranda authored 7 years ago and Olivier Fourdan committed 7 years ago

Bug: 14240

Adam Purkrt authored 7 years ago and Olivier Fourdan committed 7 years ago

Bug: 14181

The comparison is corrected, closing a one pixel gap between
TILE_LEFT and TILE_UP_LEFT and between TILE_RIGHT and TILE_UP_RIGHT.

169 translated messages.

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

168 translated messages, 1 untranslated message.

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

169 translated messages.

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

169 translated messages.

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

169 translated messages.

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

169 translated messages.

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

169 translated messages.

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

169 translated messages.

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

169 translated messages.

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

169 translated messages.

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

169 translated messages.

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

169 translated messages.

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

169 translated messages.

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

169 translated messages.

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

169 translated messages.

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

Bug 14164

Still need to raise the window on activate when using focus follow mode
otherwise.

Adam Purkrt authored 7 years ago and Olivier Fourdan committed 7 years ago

Bug: 14174

To keep the distance of the grip from the edges of the window
in proportion when unmaximizing/untiling while moving the window,
the grip position is recalculated using pxratio and pyratio.

Bug 14164

This is a regression introduced by 3877bf45, where we would differ
raising the window until it's focused.

When using click to focus, activating a transient window would raise
only that transient and not its ancestor, if any.

Change the logic to raise the ancestor if it's different from the
requested window itself.

169 translated messages.

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

Would break --enable-debug=full as this induces -Werror.

No need to have that public, so we can please the compiler.

Adam Purkrt authored 7 years ago and Olivier Fourdan committed 7 years ago

Bug: 11960

This patch fixes the erratic behaviour when unmaximizing a window by
dragging it from the absolute top.

clientToggleMaximized is now called with each motion event if
a window is maximized, hence it is always unmaximized before possibly
toggling maximization again in clientTile further down.