marco, branch v1.19.1 MATE default window manager release 1.19.1 2017-09-04T19:02:20+00:00 raveit65 mate@raveit.de 2017-09-04T19:02:20+00:00 f2a4040524b6dd9a0441b8dbd9b7378e5de0c1ea 






sync with transifex
2017-09-04T18:55:39+00:00

raveit65
mate@raveit.de

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

3c074836967eac24ce7fa93a3db930bcceba7051












Store a window flag when user resizes from tiled
2017-08-30T19:13:58+00:00

Victor Kareh
vkareh@vkareh.net

2017-08-30T19:13:58+00:00

f396a2bebc9c365527c5c6e4d4d489879e8bbea4

Use that flag to retain the correct window size when performing other
operations. Reset when re-tiling.





Use that flag to retain the correct window size when performing other
operations. Reset when re-tiling.







Allow tiled windows to be resized horizontally
2017-08-29T19:36:19+00:00

Victor Kareh
vkareh@vkareh.net

2017-08-29T19:36:19+00:00

c577f51e1e1258f8a6c55764a8b86d3421c466e7

Determine whether the user is initiating a resize action on a tiled
window. If the user is trying to grab the window for resizing
horizontally from the edge that's farther away from the screen edge,
allow the resize to occur. Otherwise maintain the current tile geometry.

Also modified the window hints to allow resizing from the window menu.

Fixes #250





Determine whether the user is initiating a resize action on a tiled
window. If the user is trying to grab the window for resizing
horizontally from the edge that's farther away from the screen edge,
allow the resize to occur. Otherwise maintain the current tile geometry.

Also modified the window hints to allow resizing from the window menu.

Fixes #250







gtk 3.22: avoid deprecated gdk_screen_get_monitor... functions:
2017-08-22T05:56:34+00:00

ZenWalker
scow@riseup.net

2017-08-14T14:48:02+00:00

a5439d2175395763e06e8bec10ad7b914742882a

avoid deprecated:

gdk_screen_get_monitor_geometry
gdk_screen_get_monitor_at_point





avoid deprecated:

gdk_screen_get_monitor_geometry
gdk_screen_get_monitor_at_point







avoid deprecated gdk_screen_width/height
2017-08-18T06:16:06+00:00

ZenWalker
scow@riseup.net

2017-08-11T00:51:02+00:00

f0541e3dfda29c26fe14c9c9117f95c49006c75c












avoid deprecated gdk_screen_get_width
2017-08-18T06:16:06+00:00

ZenWalker
scow@riseup.net

2017-08-08T23:30:37+00:00

d18c2fb4acb58c408c01700682b9922de86e8b2f












display: don't use deprecated GDK_DEVICE_MANAGER
2017-08-14T15:39:27+00:00

raveit65
mate@raveit.de

2017-08-14T13:07:42+00:00

c64a516cbca7b8d07e5de0af9223ae0199e18857

use GtkSeat for > gtk+-3.20





use GtkSeat for > gtk+-3.20







tools: remove marco-mag and marco-grayscaletools
2017-08-14T14:19:04+00:00

raveit65
mate@raveit.de

2017-08-14T14:19:04+00:00

fc513ed9c042f2bcf80a196a38c2f4db2c45252d

Those were never used in MATE and have a lot of deprecated functions.
Already droped in metacity.
https://git.gnome.org/browse/metacity/commit/?id=b580e3e





Those were never used in MATE and have a lot of deprecated functions.
Already droped in metacity.
https://git.gnome.org/browse/metacity/commit/?id=b580e3e







Fix synthetic keybinding/button-grab window (#342)
2017-08-14T10:31:10+00:00

Victor Kareh
vkareh@vkareh.net

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

680dca33ba526ae0d2dc333ac26a1c5872d86120

* 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