mate-desktop - Library with common API for various MATE modules

Age	Commit message (Collapse)	Author	Files	Lines
2024-02-12	tx: sync with transifex	raveit65	1	-43/+45

2024-02-02	releases 1.27.4v1.27.4	raveit65	3	-2/+17

2024-02-02	tx: sync with transifex	raveit65	13	-65/+114

2024-01-23	ci: use ubuntu jammy as docker	raveit65	1	-1/+1

2023-10-19	mate-colorsel: Fix compilation warnings use rgba replace color	zhuyaliang	4	-209/+162

2023-10-12	meson: Add meson support for static library	zhuyaliang	1	-1/+1

2023-10-11	Fix compilation warning replace gtk_style_context_get_background_color	zhuyaliang	2	-3/+9

2023-10-10	wayland: fix uninitialized variable	lukefromdc	1	-0/+4
	We still have sn_display in the runtime checks to determine whether to call the startup notification, so we have to initialize it to NULL in the wayland case
2023-10-09	mate-rr-labeler: Fix compilation warnings use css replace ↵	zhuyaliang	1	-1/+21
	gtk_widget_override_color
2023-10-09	mate-colorseldialog: Fix compilation warnings remove deprecated function	zhuyaliang	1	-3/+1

2023-10-08	Add meson build libstartup-notification support type is auto	zhuyaliang	2	-4/+6
	Fix https://github.com/mate-desktop/mate-desktop/issues/570
2023-10-08	Remove useless mate_color_button apis	zhuyaliang	7	-1080/+1

2023-10-05	Fix MATE_DESKTOP_CHECK_VERSION	Colomban Wendling	3	-8/+7
	Not that I know anybody that wants it though.
2023-10-05	Remove useless code	zhuyaliang	1	-10/+0

2023-10-05	Rename libmate-desktop/{mate-desktop.h => mate-desktop.h.in} add ↵	zhuyaliang	3	-3/+15
	MATE_DESKTOP_VERSION marco
2023-09-17	release 1.27.3v1.27.3	raveit65	3	-2/+8

2023-09-17	tx: drop tzm language which caused the build fail	raveit65	1	-1434/+0

2023-09-17	tx: sync with transifex	raveit65	119	-1238/+1215

2023-09-15	add xdg-desktop-portal config file	raveit65	6	-1/+15

2023-09-15	Fix ninja test symbols check FAIL	zhuyaliang	1	-0/+1

2023-09-02	tx: update resources	raveit65	1	-10/+10

2023-08-23	release 1.27.2v1.27.2	raveit65	3	-4/+10

2023-08-23	tx: pull with transifex	raveit65	8	-20/+29

2023-08-11	desktop-item: limit startup notification to x11	lukefromdc	1	-46/+52
	Wrap all startup notification calls in x11-only conditional blocks This is x11-specific code, so don't try to run it outside of x11
2023-07-02	Initial support for showing a caja desktop in wayland	lukefromdc	1	-1/+4
	*put XKillClient and gdk_x11_screen_get_xscreen behind x11-only runtime checks
2023-04-03	release 1.27.1v1.27.1	raveit65	3	-2/+7

2023-04-03	tx: sync with transifex	raveit65	120	-243/+1765

2023-04-02	Add mate image menu item apis	zhuyaliang	8	-3/+721

2022-11-11	release 1.27.0v1.27.0	mbkma	3	-2/+30

2022-11-11	tx: sync with transifex	mbkma	118	-11344/+14492

2022-11-09	Revert "[mate-bg] small cleanup"	Colomban Wendling	1	-9/+8
	It is not possible to use the `list` pointer after it has been deleted, so the "cleanup" this commit made lead to using freed memory if any item actually got clean up. This "cleanup" also don't seem meaningful to me, as all it does otherwise is trade an assignation for a redundant test -- either of which the compiler might happily optimize out. This reverts commit 47426c90d10e9f738ecf89f35db94ca8deff55e0.
2022-10-29	tx: update resource	mbkma	1	-95/+109

2022-10-28	tx: migrate config file	mbkma	2	-6/+16

2022-08-20	mate-desktop-item: time_t mtime -> gint64 mtime	rbuj	1	-5/+5
	The timestamp is compared with g_file_info_get_attribute_uint64 in mate_desktop_item_get_file_status (const MateDesktopItem *item)
2022-08-20	mate-bg: time_t mtime -> gint64 mtime	rbuj	1	-19/+8
	The timestamp is retrieved with g_file_info_get_attribute_uint64 in get_mtime (const char *filename)
2022-08-20	Fix implicit conversion changes signedness: 'gboolean' to 'guint'	rbuj	2	-3/+3

2022-08-20	mate-desktop-thumbnail: fix memory leak	rbuj	1	-0/+1

2022-08-20	Fix build warnings about missing field initializer	rbuj	2	-4/+4

2022-08-20	mate-bg: fix memory leak	rbuj	1	-3/+7

2022-08-20	mate-bg: Dereference of null pointer	rbuj	1	-1/+1

2022-08-20	configure.ac: The macro 'AC_HELP_STRING' is obsolete	rbuj	1	-3/+3

2022-08-20	mate-desktop-item: macro is not used [-Wunused-macros]	rbuj	1	-2/+0

2022-08-20	mate-colorsel: macro is not used [-Wunused-macros]	rbuj	1	-2/+0

2022-08-20	mate-bg: macro is not used [-Wunused-macros]	rbuj	1	-4/+0

2022-08-15	mate-colorbutton: fix -Wenum-conversion warning	rbuj	1	-1/+1

2022-08-15	mate-rr: fix -Wsign-compare warning	rbuj	1	-4/+4

2022-08-15	mate-rr-config: fix -Wsign-compare warning	rbuj	1	-2/+2

2022-08-15	mate-bg: fix -Wsign-compare warning	rbuj	1	-1/+1

2022-08-15	display-name: fix -Wsign-compare warning	rbuj	1	-2/+2

2022-08-08	Add setting for adjustment of audio volume above 100 per cent: Part 1	Gordon Norman Squash	1	-0/+12
	There is often a need for the user to increase the audio playback volume above the volume level known as "100% volume". While increasing the audio volume above 100% can result in degraded audio quality, sometimes the audio was, for example, originally recorded at an extremely low volume, and the user has no other option to clearly hear the audio. Unfortunately, most MATE applications with volume controls do not allow the user to set the volume level above 100%. For example, the main MATE Sound Preferences dialog lets you set the audio volume beyond 100% (when possible), whereas the Volume Control Applet, Volume Control status icon, and special "multimedia" volume control keys do not. In fact, if the user even tries to change the volume using any of the latter methods, and the current volume level is above 100%, these latter methods will all reduce the volume to 100%, even if the user tried to increase the volume! This is part 1 of a patch to change this situation. All that this patch does is add a new, standard MATE setting which determines whether the user should be allowed to set the audio volume above 100%. The rest of the functionality of this patch is in other commits / pull requests.