<feed xmlns='http://www.w3.org/2005/Atom'>
<title>marco/src, branch v1.26.0</title>
<subtitle>MATE default window manager</subtitle>
<link rel='alternate' type='text/html' href='http://git.mate-desktop.org/marco/'/>
<entry>
<title>tabpopup: fix cairo surface leak</title>
<updated>2021-07-09T13:53:23+00:00</updated>
<author>
<name>Faidon Liambotis</name>
<email>paravoid@debian.org</email>
</author>
<published>2021-07-02T22:10:22+00:00</published>
<link rel='alternate' type='text/html' href='http://git.mate-desktop.org/marco/commit/?id=8f204678be6d888ad1d2904e28af1aa9f2ad8e11'/>
<id>8f204678be6d888ad1d2904e28af1aa9f2ad8e11</id>
<content type='text'>
Commit 6b05da5e49996a2101edfd703dd3f5d91011d726 introduced a Cairo
surface leak, by calling gdk_cairo_surface_create_from_pixbuf() but then
never freeing those surfaces with cairo_surface_destroy().

This manifested in leaking resources when switching between virtual
desktops, as observed using xrestop ("Pxms" column), which made the
desktop slow and ultimately unusable after a few weeks of uptime.

Fixes #685
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Commit 6b05da5e49996a2101edfd703dd3f5d91011d726 introduced a Cairo
surface leak, by calling gdk_cairo_surface_create_from_pixbuf() but then
never freeing those surfaces with cairo_surface_destroy().

This manifested in leaking resources when switching between virtual
desktops, as observed using xrestop ("Pxms" column), which made the
desktop slow and ultimately unusable after a few weeks of uptime.

Fixes #685
</pre>
</div>
</content>
</entry>
<entry>
<title>window: add support for _GNOME_WM_STRUT_AREA</title>
<updated>2021-06-07T18:09:03+00:00</updated>
<author>
<name>raveit65</name>
<email>mate@raveit.de</email>
</author>
<published>2021-04-10T14:37:40+00:00</published>
<link rel='alternate' type='text/html' href='http://git.mate-desktop.org/marco/commit/?id=3ed0ddb242a4804cd7fcfcfcf39a47766eaa816d'/>
<id>3ed0ddb242a4804cd7fcfcfcf39a47766eaa816d</id>
<content type='text'>
In addition to existing properties use also new _GNOME_WM_STRUT_AREA
property that allows creating struts between monitors.

https://mail.gnome.org/archives/wm-spec-list/2018-December/msg00000.html
https://gitlab.freedesktop.org/xdg/xdg-specs/merge_requests/22

origin commit:
https://gitlab.gnome.org/GNOME/metacity/commit/922de13
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
In addition to existing properties use also new _GNOME_WM_STRUT_AREA
property that allows creating struts between monitors.

https://mail.gnome.org/archives/wm-spec-list/2018-December/msg00000.html
https://gitlab.freedesktop.org/xdg/xdg-specs/merge_requests/22

origin commit:
https://gitlab.gnome.org/GNOME/metacity/commit/922de13
</pre>
</div>
</content>
</entry>
<entry>
<title>screen: add support for _GTK_WORKAREAS_Dn</title>
<updated>2021-06-07T18:09:03+00:00</updated>
<author>
<name>raveit65</name>
<email>mate@raveit.de</email>
</author>
<published>2021-04-10T12:21:30+00:00</published>
<link rel='alternate' type='text/html' href='http://git.mate-desktop.org/marco/commit/?id=4e4fd6c512423b16640914b33192a32f290b0ef1'/>
<id>4e4fd6c512423b16640914b33192a32f290b0ef1</id>
<content type='text'>
In addition to existing _NET_WORKAREA property set also new
_GTK_WORKAREAS_Dn property where n is desktop number (between 0
and _NET_NUMBER_OF_DESKTOPS - 1).

https://mail.gnome.org/archives/wm-spec-list/2018-December/msg00000.html
https://gitlab.freedesktop.org/xdg/xdg-specs/merge_requests/22

origin commit:
https://gitlab.gnome.org/GNOME/metacity/-/commit/3d8b03d
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
In addition to existing _NET_WORKAREA property set also new
_GTK_WORKAREAS_Dn property where n is desktop number (between 0
and _NET_NUMBER_OF_DESKTOPS - 1).

https://mail.gnome.org/archives/wm-spec-list/2018-December/msg00000.html
https://gitlab.freedesktop.org/xdg/xdg-specs/merge_requests/22

origin commit:
https://gitlab.gnome.org/GNOME/metacity/-/commit/3d8b03d
</pre>
</div>
</content>
</entry>
<entry>
<title>window: Do not render shadows on left/right tiled windows</title>
<updated>2021-06-04T15:30:50+00:00</updated>
<author>
<name>Martin Wimpress</name>
<email>code@flexion.org</email>
</author>
<published>2021-01-30T11:21:39+00:00</published>
<link rel='alternate' type='text/html' href='http://git.mate-desktop.org/marco/commit/?id=4f567598327e9fdc50eec37ef286c62415a6677f'/>
<id>4f567598327e9fdc50eec37ef286c62415a6677f</id>
<content type='text'>
This pull request prevents shadows being rendered for left and right side titled windows. This behaviour is consistent with maximised windows, which also do not render shadows.

The rationale for this change is so that when two windows are titled along side each other, it prevents central shadows bleeding into the touching points of the windows.

metacity-theme-x.xml has provision to style left/right titled windows. This patch makes it possible to to create window themes that present clean side-by-side tiled windows.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This pull request prevents shadows being rendered for left and right side titled windows. This behaviour is consistent with maximised windows, which also do not render shadows.

The rationale for this change is so that when two windows are titled along side each other, it prevents central shadows bleeding into the touching points of the windows.

metacity-theme-x.xml has provision to style left/right titled windows. This patch makes it possible to to create window themes that present clean side-by-side tiled windows.
</pre>
</div>
</content>
</entry>
<entry>
<title>iconcache: Use GDesktopAppInfo to find correct application icons</title>
<updated>2021-06-04T15:02:28+00:00</updated>
<author>
<name>Victor Kareh</name>
<email>vkareh@redhat.com</email>
</author>
<published>2021-05-26T18:14:59+00:00</published>
<link rel='alternate' type='text/html' href='http://git.mate-desktop.org/marco/commit/?id=60e6fbfb093d63c46ca8e77750c54f31c9780c1c'/>
<id>60e6fbfb093d63c46ca8e77750c54f31c9780c1c</id>
<content type='text'>
Some files do not report their application icons correctly in the window
properties. This patch allows the marco UI to search for the
corresponding .desktop file and render the icon in the desktop info on
both the alt-tab popup and the window mini-icon.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Some files do not report their application icons correctly in the window
properties. This patch allows the marco UI to search for the
corresponding .desktop file and render the icon in the desktop info on
both the alt-tab popup and the window mini-icon.
</pre>
</div>
</content>
</entry>
<entry>
<title>window: Track window rectangle before corner tiling</title>
<updated>2021-05-28T21:11:35+00:00</updated>
<author>
<name>Victor Kareh</name>
<email>vkareh@redhat.com</email>
</author>
<published>2021-05-27T11:16:39+00:00</published>
<link rel='alternate' type='text/html' href='http://git.mate-desktop.org/marco/commit/?id=4ccf24665bfb3501e727f133a5f7c59ade2154d2'/>
<id>4ccf24665bfb3501e727f133a5f7c59ade2154d2</id>
<content type='text'>
When corner-tiling a maximized window, we should keep track of the saved
rectangle so that tiling does not reset our window size. Otherwise,
untiling the previously maximized window will end up with an unmaximized
full-size window, rather than the original window size.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
When corner-tiling a maximized window, we should keep track of the saved
rectangle so that tiling does not reset our window size. Otherwise,
untiling the previously maximized window will end up with an unmaximized
full-size window, rather than the original window size.
</pre>
</div>
</content>
</entry>
<entry>
<title>window: Track window rectangle before tiling</title>
<updated>2021-05-26T18:25:31+00:00</updated>
<author>
<name>Victor Kareh</name>
<email>vkareh@redhat.com</email>
</author>
<published>2021-04-30T13:49:36+00:00</published>
<link rel='alternate' type='text/html' href='http://git.mate-desktop.org/marco/commit/?id=fa2afbfd60443051e377193b52df54c080df7202'/>
<id>fa2afbfd60443051e377193b52df54c080df7202</id>
<content type='text'>
When tiling a maximized window, we should keep track of the saved
rectangle so that tiling does not reset our window size. Otherwise,
untiling the previously maximized window will end up with an unmaximized
full-size window, rather than the original window size.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
When tiling a maximized window, we should keep track of the saved
rectangle so that tiling does not reset our window size. Otherwise,
untiling the previously maximized window will end up with an unmaximized
full-size window, rather than the original window size.
</pre>
</div>
</content>
</entry>
<entry>
<title>window: Only unmaximize when the window is already maximized.</title>
<updated>2021-04-30T13:47:57+00:00</updated>
<author>
<name>Zhiyi Zhang</name>
<email>zzhang@codeweavers.com</email>
</author>
<published>2021-04-14T08:03:31+00:00</published>
<link rel='alternate' type='text/html' href='http://git.mate-desktop.org/marco/commit/?id=60f49ae5a272b737a944065e4199c8b2c8eec8b1'/>
<id>60f49ae5a272b737a944065e4199c8b2c8eec8b1</id>
<content type='text'>
When handling a ClientMessage event that removes _NET_WM_STATE_MAXIMIZED_HORZ
or _NET_WM_STATE_MAXIMIZED_VERT from _NET_WM_STATE, marco always restore the
window rectangle to the saved rectangle. So if an application window is already
unmaximized and the application sends such a ClientMessage event, marco will
reset the window rectangle regardless. EWMH doesn't specify what must be done
when handling such events. It seems best to avoid restoring window rectangles
like other window managers in this case.

Fix a related bug: https://bugs.winehq.org/show_bug.cgi?id=50381

This revert a change introduced by 6219f8e8bcaeefb9185a3c3f5f20de4e2fa8f18f.

Signed-off-by: Zhiyi Zhang &lt;zzhang@codeweavers.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
When handling a ClientMessage event that removes _NET_WM_STATE_MAXIMIZED_HORZ
or _NET_WM_STATE_MAXIMIZED_VERT from _NET_WM_STATE, marco always restore the
window rectangle to the saved rectangle. So if an application window is already
unmaximized and the application sends such a ClientMessage event, marco will
reset the window rectangle regardless. EWMH doesn't specify what must be done
when handling such events. It seems best to avoid restoring window rectangles
like other window managers in this case.

Fix a related bug: https://bugs.winehq.org/show_bug.cgi?id=50381

This revert a change introduced by 6219f8e8bcaeefb9185a3c3f5f20de4e2fa8f18f.

Signed-off-by: Zhiyi Zhang &lt;zzhang@codeweavers.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>window-props: g_memdup is dreprecated from glib 2.68</title>
<updated>2021-04-02T19:00:34+00:00</updated>
<author>
<name>rbuj</name>
<email>robert.buj@gmail.com</email>
</author>
<published>2021-03-25T11:09:51+00:00</published>
<link rel='alternate' type='text/html' href='http://git.mate-desktop.org/marco/commit/?id=5d48375212d816bb9e4d23efdc155ec77dbe927d'/>
<id>5d48375212d816bb9e4d23efdc155ec77dbe927d</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>warning: declaration of a variable shadows a previous local</title>
<updated>2021-03-29T12:59:30+00:00</updated>
<author>
<name>rbuj</name>
<email>robert.buj@gmail.com</email>
</author>
<published>2021-03-16T08:09:37+00:00</published>
<link rel='alternate' type='text/html' href='http://git.mate-desktop.org/marco/commit/?id=348151fd0204a4ae0aa76bc3312cf045d7a6a2dd'/>
<id>348151fd0204a4ae0aa76bc3312cf045d7a6a2dd</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
</feed>
