marco/src, branch v1.25.1 MATE default window manager window: Do not render shadows on left/right tiled windows 2021-06-04T15:30:50+00:00 Martin Wimpress code@flexion.org 2021-01-30T11:21:39+00:00 4f567598327e9fdc50eec37ef286c62415a6677f 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. 
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.
iconcache: Use GDesktopAppInfo to find correct application icons 2021-06-04T15:02:28+00:00 Victor Kareh vkareh@redhat.com 2021-05-26T18:14:59+00:00 60e6fbfb093d63c46ca8e77750c54f31c9780c1c 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. 
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.
window: Track window rectangle before corner tiling 2021-05-28T21:11:35+00:00 Victor Kareh vkareh@redhat.com 2021-05-27T11:16:39+00:00 4ccf24665bfb3501e727f133a5f7c59ade2154d2 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. 
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.
window: Track window rectangle before tiling 2021-05-26T18:25:31+00:00 Victor Kareh vkareh@redhat.com 2021-04-30T13:49:36+00:00 fa2afbfd60443051e377193b52df54c080df7202 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. 
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.
window: Only unmaximize when the window is already maximized. 2021-04-30T13:47:57+00:00 Zhiyi Zhang zzhang@codeweavers.com 2021-04-14T08:03:31+00:00 60f49ae5a272b737a944065e4199c8b2c8eec8b1 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 <zzhang@codeweavers.com> 
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 <zzhang@codeweavers.com>
window-props: g_memdup is dreprecated from glib 2.68 2021-04-02T19:00:34+00:00 rbuj robert.buj@gmail.com 2021-03-25T11:09:51+00:00 5d48375212d816bb9e4d23efdc155ec77dbe927d 






warning: declaration of a variable shadows a previous local
2021-03-29T12:59:30+00:00

rbuj
robert.buj@gmail.com

2021-03-16T08:09:37+00:00

348151fd0204a4ae0aa76bc3312cf045d7a6a2dd












testasyncgetprop: Mismatching the argument type 'unsigned long'
2021-03-18T21:42:31+00:00

rbuj
robert.buj@gmail.com

2021-02-22T17:35:36+00:00

0dee04e5b88d941bb727ffdc80d50966ca48d9f6

and conversion specifier 'ld', reported by Apache NetBeans IDE





and conversion specifier 'ld', reported by Apache NetBeans IDE







bell: Unused static function 'bell_flash_screen'
2021-03-18T21:41:28+00:00

rbuj
robert.buj@gmail.com

2021-02-24T12:52:42+00:00

880f50be8abe386c27305351f1f47a0fc30780a3












frames: Unused static functions 'get_client_region', 'get_frame_region'
2021-03-13T19:37:35+00:00

rbuj
robert.buj@gmail.com

2021-02-24T12:54:40+00:00

d9903e20a770e024d88250b36424054b0bc43a38