marco, branch v1.18.2 MATE default window manager release 1.18.2 2017-11-06T09:31:05+00:00 raveit65 mate@raveit.de 2017-11-06T09:31:05+00:00 f7d762523b1ec7e98618f6158de16ddc86f7f602 






sync with transifex
2017-11-06T08:37:16+00:00

raveit65
mate@raveit.de

2017-11-06T08:36:31+00:00

e812845541c5acbc9d2e5185789fe1e6b5f4f144












sync with transifex
2017-11-06T08:34:37+00:00

raveit65
mate@raveit.de

2017-09-04T18:55:39+00:00

aaa857b8b6239d9d5f82bd6b5d7bffeb8f7eb4b7












Fix synthetic keybinding/button-grab window (#342)
2017-08-18T07:17:31+00:00

Victor Kareh
vkareh@vkareh.net

2017-08-14T10:31:10+00:00

841f6cc41ab3389d12912dbcb166744ab3eab688

* 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





* 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







ui: Fix invalid object construction in frames
2017-06-30T20:25:03+00:00

Ikey Doherty
ikey@solus-project.com

2017-06-20T21:07:16+00:00

71950df523c575922a2d83ba54a7009c10c3895b

This legacy construct was carried over from the gtk2/gtk3 port, and
attempts to initialise MetaFrames with a GtkWindow `type` property.
This property doesn't actually exist, and will cause marco to completely
crash when running with `MARCO_DEBUG=1` for local build testing.

Signed-off-by: Ikey Doherty <ikey@solus-project.com>





This legacy construct was carried over from the gtk2/gtk3 port, and
attempts to initialise MetaFrames with a GtkWindow `type` property.
This property doesn't actually exist, and will cause marco to completely
crash when running with `MARCO_DEBUG=1` for local build testing.

Signed-off-by: Ikey Doherty <ikey@solus-project.com>







release 1.18.1
2017-05-10T15:13:03+00:00

raveit65
mate@raveit.de

2017-05-10T15:13:03+00:00

85a43df0d3943c9fe2db32fc9578da1a4e743b63












sync with transifex
2017-05-10T15:07:38+00:00

raveit65
mate@raveit.de

2017-05-10T15:06:37+00:00

ecf58e3f217e98a83f5fb30a1dd7af600489b789












ui: avoid deprecated GdkDeviceManager
2017-05-10T15:04:22+00:00

Alberts Muktupāvels
alberts.muktupavels@gmail.com

2017-04-23T11:00:23+00:00

024c1e487f90696bb66da4574dc607d96c5f5bbd

taken from:
https://git.gnome.org/browse/metacity/commit/?id=7ec9a6f





taken from:
https://git.gnome.org/browse/metacity/commit/?id=7ec9a6f







build: Use non-deprecated feature test macros
2017-05-10T15:03:59+00:00

Dmitry Shachnev
mitya57@gmail.com

2017-04-23T09:28:37+00:00

146ba74e9e76f0c79af1dbefde5573cad65529ec

_SVID_SOURCE has been deprecated in newer versions of glibc breaking -WError;
the recommended replacement of _DEFAULT_SOURCE is fairly new, so switch to
_XOPEN_SOURCE instead.

Based on mutter commits b159d6a5e17219557574defb6c3788d9b0c39757
and b159d6a5e17219557574defb6c3788d9b0c39757.

https://bugzilla.gnome.org/show_bug.cgi?id=763782

taken from:
https://git.gnome.org/browse/metacity/commit/?id=56bcf350fb599ec2caf68af4f0f92b1c3999027c





_SVID_SOURCE has been deprecated in newer versions of glibc breaking -WError;
the recommended replacement of _DEFAULT_SOURCE is fairly new, so switch to
_XOPEN_SOURCE instead.

Based on mutter commits b159d6a5e17219557574defb6c3788d9b0c39757
and b159d6a5e17219557574defb6c3788d9b0c39757.

https://bugzilla.gnome.org/show_bug.cgi?id=763782

taken from:
https://git.gnome.org/browse/metacity/commit/?id=56bcf350fb599ec2caf68af4f0f92b1c3999027c







tile-preview: avoid a deprecation warning
2017-05-10T15:03:41+00:00

Alberts Muktupāvels
alberts.muktupavels@gmail.com

2017-04-23T07:54:57+00:00

105abf2b5f34489bb3a5d62753c32178471379a9

Taken from:
https://git.gnome.org/browse/metacity/commit/?id=3380502





Taken from:
https://git.gnome.org/browse/metacity/commit/?id=3380502