summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2020-02-21remove warning: 'GTimeVal' is deprecatedrbuj6-50/+34
2020-02-21theme: avoid deprecated g_memmovercaridade1451-3/+3
https://gitlab.gnome.org/GNOME/glib/commit/6554c91b https://gitlab.gnome.org/GNOME/glib/commit/6e4a7fca based on https://gitlab.gnome.org/GNOME/metacity/commit/359f60a6
2020-02-21frames: don't bother painting the backgroundrcaridade1451-23/+0
GDK (and also GTK+!) do this for us already. based on https://gitlab.gnome.org/GNOME/metacity/commit/1dcde194
2020-02-20travis: update config for new travis validationraveit652-182/+183
2020-02-09release 1.24.0v1.24.0raveit652-2/+8
2020-02-09tx: sync with transifexraveit656-32/+41
2020-02-06window: handle legacy fullscreen requestsrcaridade1452-24/+30
https://gitlab.gnome.org/GNOME/metacity/commit/1fafd279006ece8cf664fd777143cdfafbefad6d window: handle legacy fullscreen requests Doing this on the actual resize requests makes more sense than handling it as a window-manager imposed constraints, so move the code accordingly. Adapted from mutter patch by Florian Müllner: https://git.gnome.org/browse/mutter/commit/?id=fba022cc06b8c7e80ef36f48d6577a251384cc4b https://bugzilla.gnome.org/show_bug.cgi?id=781946 Bug 781946 - Non-native decorated windows stuck maximised on secondary screen with Marco/Metacity
2020-02-04frame: remove unused variable 'status'rbuj1-1/+0
2020-01-22Xprops fix memory leak.rcaridade1451-7/+13
Origin commit : https://gitlab.gnome.org/GNOME/metacity/commit/c87f73f3b4413720a2f3e6a672826d3fec7f77a9 " XmbTextPropertyToTextList documentation says that XFreeStringList should be used to free the storage for the list and its contents. "
2019-12-06release 1.23.2v1.23.2raveit653-4/+54
2019-12-06tx: sync with transifexraveit65105-61837/+64267
2019-12-06Revert "compositor: fix possible crash closing/destroying window"Victor Kareh3-32/+9
This reverts commit df56628979abc17474b001c58c28c6f3637ada9d. It causes an issue where windows remain in the background even when being drawn in the foreground.
2019-12-05theme.c: Fix window control hidpi rendering for all themes.Michael Webster1-3/+15
By scaling the pixbuf when loading, existing assets can be used.
2019-12-05tabpopup: Increase max number of columnsVictor Kareh2-2/+2
2019-12-02Travis CI: add '-Wredundant-decls' to 'CFLAGS' variablePablo Barciela1-1/+1
2019-11-24travis ci: use fedora:latestraveit651-1/+1
2019-11-18tx: add fixes to makepot scriptraveit651-0/+2
2019-11-18tx: update resource for transifexraveit651-291/+301
2019-10-31window: Add optional tile size cyclingVictor Kareh6-13/+123
Adding a new option to allow tile size cycling. When enabled, using the keyboard shortcut for tiling multiple times in a row cycles the window through different sizes (1/2 -> 1/3 -> 1/4 -> 3/4 -> 2/3 -> Untiled).
2019-10-29DustBlue: strip image of all profiles and commentsrbuj13-0/+0
find . -name "*.png" -exec mogrify -strip {} ;
2019-10-27tabpopup: Fix deprecation warningsVictor Kareh1-26/+38
2019-10-27tabpopup: Change schema value rangesVictor Kareh2-7/+7
Since we're rewriting how tab popups are created, we should change the gschema value ranges so that they are more compatible with the new version.
2019-10-27tabpopup: Make workspaces compatible with OSD popupVictor Kareh2-25/+23
When drawing the workspace switcher OSD, we want it to be slightly transparent to match the OSD style. Also changed how the popup size is calculated and changed window icons to cairo surfaces.
2019-10-27tabpopup: Render window thumbnail as cairo surfaceVictor Kareh3-91/+118
Instead of converting from surface to a GdkPixbuf and then back to a surface, we keep it as a surface for the entire manipulation flow. This improves rendering speed a bit and sets the ground for a higher resolution thumbnail in the future.
2019-10-27tabpopup: Draw transparent OSD-style popupsVictor Kareh3-58/+94
2019-10-26Fix MARCO_LOCALEDIR displaying the translated messagesrbuj1-1/+1
2019-10-12WinMe theme: strip png images of all profiles and commentsrbuj10-0/+0
find . -name "*.png" -exec mogrify -strip {} \;
2019-10-11ci: set maximum compile warnings on step scan-build ./configurerbuj1-1/+1
The autogen.sh compiler warning flags are overridden in the configure step.
2019-10-08eOS theme: Add single button backgroundsrbuj6-0/+600
2019-10-08eOS theme: strip png images of all profiles and commentsrbuj20-0/+0
find . -name "*.png" -exec mogrify -strip {} \;
2019-10-08eOS theme: make transparent the button-box outer regionrbuj8-0/+0
2019-10-07theme: Render window control buttons and icons as surfacesVictor Kareh2-24/+291
When loading window control buttons and icon as pixbufs, we just set them as the source for the cairo context used to paint them. Instead, we now convert them to cairo surfaces and scale them to the correct display density before painting them. This allows us to load higher resolution assets (i.e. at twice the size) and by explicitly setting the intended size in the theme draw_ops, we can then scale them down to fit lower resolution displays, or render them at full density for HiDPI displays.
2019-10-06Travis CI: use Debian "testing" instead "sid"Pablo Barciela1-1/+1
2019-10-05travis(ci): enable notify_serversraveit651-0/+2
2019-10-01Set compiler debug flags using MATE_DEBUG_CHECKrbuj1-1/+1
--enable-debug=yes/info/profile/no By default, compiler debug flags are disabled. Test: $ ./autogen.sh && grep "^CFLAGS" config.log CFLAGS=' -Wall -Wcast-align -Wchar-subscripts -Werror=format-security -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wsign-compare -Wshadow' $ ./autogen.sh --enable-debug && grep "^CFLAGS" config.log CFLAGS=' -g -O0 -Wall -Wcast-align -Wchar-subscripts -Werror=format-security -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wsign-compare -Wshadow'
2019-10-01window decoration themes: Add Atlanta, Esco, Gorilla, Motif, Raleighrbuj34-12/+2656
2019-10-01Print CFLAGS and WARN_CFLAGS in configure summaryrbuj1-0/+2
2019-10-01Set --enable-compile-warnings=yes by defaultrbuj1-1/+1
2019-10-01 travis (ci): use --enable-compile-warnings=maximumraveit651-1/+14
- build mate-common from tarball
2019-10-01Use WARN_CFLAGS which are only set with --enable-compiler-warningsrbuj4-15/+11
It removes --enable-more-warnings, since it is recommended to use --enable-compile-warnings=maximum
2019-09-24testboxes: Fix find_closest_point_to_line() testVictor Kareh1-4/+6
Eeeks, testing floating points for equality ... upstream commit: https://gitlab.gnome.org/GNOME/mutter/commit/0fccb0fc8
2019-09-19remove warnings: function declaration isn’t a prototyperbuj1-16/+16
core/testboxes.c:34:1: warning: function declaration isn’t a prototype [-Wstrict-prototypes] core/testboxes.c:103:1: warning: function declaration isn’t a prototype [-Wstrict-prototypes] core/testboxes.c:120:1: warning: function declaration isn’t a prototype [-Wstrict-prototypes] core/testboxes.c:148:1: warning: function declaration isn’t a prototype [-Wstrict-prototypes] core/testboxes.c:167:1: warning: function declaration isn’t a prototype [-Wstrict-prototypes] core/testboxes.c:190:1: warning: function declaration isn’t a prototype [-Wstrict-prototypes] core/testboxes.c:589:1: warning: function declaration isn’t a prototype [-Wstrict-prototypes] core/testboxes.c:681:1: warning: function declaration isn’t a prototype [-Wstrict-prototypes] core/testboxes.c:725:1: warning: function declaration isn’t a prototype [-Wstrict-prototypes] core/testboxes.c:842:1: warning: function declaration isn’t a prototype [-Wstrict-prototypes] core/testboxes.c:904:1: warning: function declaration isn’t a prototype [-Wstrict-prototypes] core/testboxes.c:1021:1: warning: function declaration isn’t a prototype [-Wstrict-prototypes] core/testboxes.c:1154:1: warning: function declaration isn’t a prototype [-Wstrict-prototypes] core/testboxes.c:1243:1: warning: function declaration isn’t a prototype [-Wstrict-prototypes] core/testboxes.c:1344:1: warning: function declaration isn’t a prototype [-Wstrict-prototypes] core/testboxes.c:1396:1: warning: function declaration isn’t a prototype [-Wstrict-prototypes]
2019-09-19Remove warning: format not a string literal, argument types not checkedrbuj1-7/+1
ui/tabpopup.c:176:7: warning: format not a string literal, argument types not checked [-Wformat-nonliteral] 176 | tmp = g_markup_printf_escaped (formatter, str); | ^~~
2019-09-15build: add --enable-more-warnings configure flagrbuj3-78/+17
- Remove -ansi from CFLAGS. - By default, CFLAGS: -Wall -Wcast-align -Wchar-subscripts -Werror=format-security -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wsign-compare -Wshadow - If --enable-more-warnings, add -Wextra to CFLAGS. - Requires autoconf-archive package.
2019-09-10build: Remove rationales.txt from EXTRA_DIST targetrbuj1-1/+1
2019-09-10Fix use of RBGA visual in frame.c when compositing is not in uselukefromdc1-37/+1
Use the window's visual in all cases, fix problems with drivers forcing use of blit rather than pageflip mode when comppositing is not used or window is unredirected Apply https://gitlab.gnome.org/GNOME/metacity/commit/5863176a2bd659c8d9a3d1c7b023a27c1a8c0aa5
2019-09-10drop old and obsolete rationales.txtraveit651-79/+0
2019-09-06Travis CI: clang: -enable-checker alpha.deadcode.UnreachableCodePablo Barciela1-0/+1
2019-09-04window.c: remove unused variablePavel Shlyak1-3/+0
2019-08-31 display.c: add missing "break"Pavel Shlyak1-1/+1