~mate-desktop/mate-desktop/+git/marco:1.18

Branch merges

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related charm recipes

be42b58... by Vlad Orlov on 2018-03-17

release 1.18.3

144dce8... by Vlad Orlov on 2018-01-23

build: drop unneeded pangoxft requirement

closes https://github.com/mate-desktop/marco/issues/288

6243525... by Victor Kareh on 2018-03-07

Fix mismatched enums in keybinding detection for switch-panels and switch-panels-backward

0dd9689... by Jan Niklas Hasse on 2018-01-02

compositor: don't try to paint window that is not viewable, fix #324

Based on metacity commit: a0b8c85c4c0cfb9a378d7c5554af15fdd7703155
From: Alberts Muktupāvels <email address hidden>

36f7928... by Jan Burgmeier <email address hidden> on 2017-11-08

XFIXES regions are leaked during paint_windows if more than one
META_COMP_WINDOW_DESKTOP is available (#329)

a17f588... by Omar Zeidan <email address hidden> on 2018-02-12

Fixes move_to_center moving window between monitors

f7d7625... by raveit65 on 2017-11-06

release 1.18.2

e812845... by raveit65 on 2017-11-06

sync with transifex

aaa857b... by raveit65 on 2017-09-04

sync with transifex

841f6cc... by Victor Kareh on 2017-08-14

Fix synthetic keybinding/button-grab window (#342)

* Determine focused window when processing synthetic events

When a client is passively grabbing keybindings that it does not need,
it sends them up for other clients to process.

Often in this situation, the event contains the wrong window (either
root, for global keybindings, or the original client itself). This means
that Marco will attempt to process the event for the wrong window.

This is not an issue for global keybindings within Marco, as the focused
window does not matter. However, for shortcuts that operate directly on
specific windows, the event gets lost.

This change addresses this by determining what the currently-focused
window is, regardless of which client forwarded the event.

* Determine window under pointer when processing synthetic events

When a client is passively grabbing mouse clicks that it does not need,
it sends them up for other clients to process.

Often in this situation, the event contains the wrong window (either
root, for global keybindings, or the original client itself). This means
that Marco will attempt to process the event for the wrong window.

This change addresses this by determining what the current window under
the mouse pointer is, regardless of which client forwarded the event.

* Remove unused development data