summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2024-02-02releases 1.27.1v1.27.1raveit653-3/+21
2024-02-02tx: sync with transifexraveit65105-25204/+26356
2024-01-23ci: use ubuntu jammy as dockerraveit651-1/+1
2023-10-19tabpopup: Use more contrasting background when not compositedColomban Wendling1-5/+16
When composited, the tab popup uses an OSD style which typically has a dark background, so we use a light background highlight color. However, when not composited the popup uses a light color and should thus use a dark highlight. This was done for the workspace popup, but not for the window one, leading to the highlight being hardly visible in several themes.
2023-10-14Allow applications to raise windows when raise_on_click is off.ns2-3/+2
This is Metacity commit 50358a95 ("Allow applications to raise windows when raise_on_click is off. Closes #445447.") applied to Marco without modification. It also includes a change to the GSettings key's description to remove the now obsolete warning on the raise-on-click key, & replaces it with an actually useful description. This is copied from the equivalent key in gsettings-desktop-schemas. Fixes: https://github.com/mate-desktop/marco/issues/762
2023-10-05replace deprecated gtk_image_menu_itemraveit654-3/+42
2023-09-01tx: update resourcesraveit651-234/+244
2023-08-17ui/tabpopup: likewise only enable compositing code if available.Mihai Moldovan3-2/+11
2023-08-17ui/frames: check that compositing is not only requested, but also available.Mihai Moldovan5-22/+33
Enabling code that is supposed to be used in compositing conditions is harmful if compositing is not actually available. Just checking the preference is not enough to make sure that compositing is available - the X server might be missing crucial extensions for compositing to work, which in turn correctly disables the internal compositor. The end result is graphical issues like black borders around windows in such situations. Make sure that compositing is both requested AND available to fix this bug.
2023-07-19Fix losing title of windows with a 3 or 4 bytes first characterColomban Wendling1-1/+1
Fixes #757.
2023-04-20meson: Enable verbose mode support by default in line with AutoconfColomban Wendling1-2/+2
Verbose mode is not active by default when running Marco, but can be toggled dynamically to help debug issues, possibly as they happen. This should only be disabled for very performance-sensitive or size-sensitive builds, but not for the regular case where it can be very useful to debug a user issue.
2023-04-20Revert "build: by default disable also the verbose mode for autoconf"Colomban Wendling1-3/+3
Verbose logging shouldn't require a rebuild, as it can help debugging user problems. This reverts commit 397e31879bf79861a1a21ec4e2a75017e243d34b.
2023-04-15configure.ac: The macro 'AC_HELP_STRING' is obsoleterbuj1-9/+9
2023-02-10Show correct window title when owned by superuser. Issue #749insaner1-1/+1
2023-01-18Add setting to raise windows on alt+tab popupsparkida5-3/+41
2023-01-14Test if XResQueryClientIds() is available before using it.Joakim Tjernlund1-0/+2
Needed for X2Go as it does not have XRES 1.2 extension.
2023-01-14Test Xres 1.2 is presentJoakim Tjernlund2-2/+13
Before using any Xres extension one must call XResQueryExtension() Also make sure Xres 1.2 is available as marco need XResQueryClientIds()
2023-01-14test return value from XResQueryClientIds()Joakim Tjernlund1-5/+6
2022-11-11release 1.27.0v1.27.0mbkma3-2/+30
2022-11-11tx: sync with transifexmbkma112-10567/+11952
2022-11-07replace _NET_WM_PID with XResGetClientPid (#741)Jan Novotný4-1/+54
window-props: use XResQueryClientIds to get pid _NET_WM_PID is unreliable! It can be faked or pid might be from different namespace. Ignore _NET_WM_PID and use XResQueryClientIds to get pid. https://gitlab.gnome.org/GNOME/metacity/-/commit/bcbe966511362a8eb8c8c64035ab160086c931f8
2022-11-07Always bring into foreground the previous window after closing oneBalazs Endresz1-1/+1
When opening and then closing certain applications the focus was correctly regained by the previous window but it wasn't brought into the foreground. To fix this we call meta_workspace_focus_default_window() for both NotifyDetailNone and NotifyPointerRoot. These two are always mentioned together in the X docs: https://tronche.com/gui/x/xlib/events/input-focus/normal-and-grabbed.html Some programs will have NotifyDetailNone when closed, while others end up with NotifyPointerRoot.
2022-10-29tx: update resourcembkma1-48/+52
2022-10-28tx: migrate config filembkma2-6/+16
2022-10-15window: do not disable fullscreen for dialogsAlberts Muktupāvels1-1/+2
fixes https://github.com/mate-desktop/marco/issues/735
2022-08-15ui: avoid 'g_object_unref (NULL)'rbuj1-3/+5
2022-04-07marco: Add cmdline option --no-keybindings for disabling all key bindings ↵Mike Gabriel2-0/+14
directly on WM startup. The marco WM is used in Arctica Greeter [1]. There recently has a security issue been detected where people could open applications via marco keybindings inside the greeter (display manager) session. . A work-around could be evoking marco-message after marco startup and disable all keybindings then. However, a more preferred fix is provided by this patch: start-up marco with keybindings disabled from the beginning.
2022-03-11boxes: fix build warning -Wstring-conversionrbuj1-28/+27
2022-03-11Fix some -Wfloat-conversion warningsrbuj9-66/+73
2022-02-19keybindings: fix build warning -Wbad-function-castrbuj1-11/+7
2022-02-13Remove TRUE, FALSE from if statementrbuj5-28/+22
2022-02-13ci: drop -Wunused-parameter compiler cflag from debian buildraveit651-1/+1
2022-01-30theme-viewer: use GTK_STYLE_PROPERTY_FONTrbuj1-2/+6
2022-01-30theme: fix memory leakrbuj1-1/+0
2022-01-27Fix implicit conversion changes signedness: 'gboolean' to 'guint'rbuj7-29/+30
2022-01-27compositor-xrender: remove unrequired g_free because of g_new0rbuj1-5/+0
2022-01-27compositor-xrender: fix memory leakrbuj1-19/+33
2022-01-27build: fix meson buildrbuj1-1/+1
2022-01-26prefs: fix memory leakrbuj1-21/+27
2021-12-30main: Add short name for version optionrbuj1-1/+1
2021-12-11Remove whitespaces before #define, #ifdef, and #endifrbuj2-4/+4
2021-10-26fix code-formatting issue of previous commitraveit651-1/+1
- drop white spaces
2021-10-23Safeguard against calling gdk_x11_window_get_xid with a NULL GdkWindowrcaridade1451-2/+5
2021-10-19README: Update gtk requirement and patch submissionTormod Volden3-7/+8
Also update HACKING Signed-off-by: Tormod Volden <[email protected]>
2021-08-04release 1.26.0v1.26.0raveit653-3/+10
2021-08-04tx: sync with transifexraveit65105-21936/+20734
2021-08-04travis-Ci: use libera.chat as notification serverraveit651-1/+1
2021-07-09tabpopup: fix cairo surface leakFaidon Liambotis1-1/+7
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
2021-06-07window: add support for _GNOME_WM_STRUT_AREAraveit657-13/+129
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
2021-06-07screen: add support for _GTK_WORKAREAS_Dnraveit652-0/+45
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