summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2023-10-05Remove useless codezhuyaliang1-10/+0
2023-10-05Rename libmate-desktop/{mate-desktop.h => mate-desktop.h.in} add ↵zhuyaliang3-3/+15
MATE_DESKTOP_VERSION marco
2023-09-17release 1.27.3v1.27.3raveit653-2/+8
2023-09-17tx: drop tzm language which caused the build failraveit651-1434/+0
2023-09-17tx: sync with transifexraveit65119-1238/+1215
2023-09-15add xdg-desktop-portal config fileraveit656-1/+15
2023-09-15Fix ninja test symbols check FAILzhuyaliang1-0/+1
2023-09-02tx: update resourcesraveit651-10/+10
2023-08-23release 1.27.2v1.27.2raveit653-4/+10
2023-08-23tx: pull with transifexraveit658-20/+29
2023-08-11desktop-item: limit startup notification to x11lukefromdc1-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-02Initial support for showing a caja desktop in waylandlukefromdc1-1/+4
*put XKillClient and gdk_x11_screen_get_xscreen behind x11-only runtime checks
2023-04-03release 1.27.1v1.27.1raveit653-2/+7
2023-04-03tx: sync with transifexraveit65120-243/+1765
2023-04-02Add mate image menu item apiszhuyaliang8-3/+721
2022-11-11release 1.27.0v1.27.0mbkma3-2/+30
2022-11-11tx: sync with transifexmbkma118-11344/+14492
2022-11-09Revert "[mate-bg] small cleanup"Colomban Wendling1-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-29tx: update resourcembkma1-95/+109
2022-10-28tx: migrate config filembkma2-6/+16
2022-08-20mate-desktop-item: time_t mtime -> gint64 mtimerbuj1-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-20mate-bg: time_t mtime -> gint64 mtimerbuj1-19/+8
The timestamp is retrieved with g_file_info_get_attribute_uint64 in get_mtime (const char *filename)
2022-08-20Fix implicit conversion changes signedness: 'gboolean' to 'guint'rbuj2-3/+3
2022-08-20mate-desktop-thumbnail: fix memory leakrbuj1-0/+1
2022-08-20Fix build warnings about missing field initializerrbuj2-4/+4
2022-08-20mate-bg: fix memory leakrbuj1-3/+7
2022-08-20mate-bg: Dereference of null pointerrbuj1-1/+1
2022-08-20configure.ac: The macro 'AC_HELP_STRING' is obsoleterbuj1-3/+3
2022-08-20mate-desktop-item: macro is not used [-Wunused-macros]rbuj1-2/+0
2022-08-20mate-colorsel: macro is not used [-Wunused-macros]rbuj1-2/+0
2022-08-20mate-bg: macro is not used [-Wunused-macros]rbuj1-4/+0
2022-08-15mate-colorbutton: fix -Wenum-conversion warningrbuj1-1/+1
2022-08-15mate-rr: fix -Wsign-compare warningrbuj1-4/+4
2022-08-15mate-rr-config: fix -Wsign-compare warningrbuj1-2/+2
2022-08-15mate-bg: fix -Wsign-compare warningrbuj1-1/+1
2022-08-15display-name: fix -Wsign-compare warningrbuj1-2/+2
2022-08-08Add setting for adjustment of audio volume above 100 per cent: Part 1Gordon Norman Squash1-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.
2022-02-13ci: drop -Wunused-parameter compiler cflag from debian buildraveit651-1/+1
2021-12-11Use a blank line at mostrbuj17-65/+0
2021-10-20Fix versionsrezso1-5/+5
mate_minor_version and mate_micro_version always 1. In addition, mate_minor / mate_minor_version and mate_micro / mate_micro_version always same.
2021-08-07fix meson versionraveit651-1/+1
closes https://github.com/mate-desktop/mate-desktop/issues/475
2021-08-03release 1.26.0v1.26.0raveit652-1/+23
2021-08-03tx: update resourceraveit651-8/+20
2021-08-03tx: sync with transifexraveit65118-6908/+13330
2021-07-21Replace the obsolete API in mate-colorsel.c filezhuyaliang1-15/+40
2021-07-19Fix compilation warningzhuyaliang4-27/+60
2021-06-21tx: update resourceraveit651-18/+18
2021-06-21update copyright to 2021raveit6513-0/+13
2021-05-30travis-ci: use ubuntu focal as host systemraveit651-1/+1
fixes build issues with fedora:latest (f34) tag.
2021-05-13MATE About: Fix off-by-one error, display yerba mate commentGordon N. Squash1-1/+1
The MATE About program is designed to display one of six messages at random each time you launch the application, showcasing the fundamental values of the MATE Project. Unfortunately, due to an off-by-one programming error introduced many years ago, only the first five messages ever get displayed; the sixth message, referring to where MATE got its name from, is never chosen. This was due to a misunderstanding of the GLib function `g_random_int_range`: The function is and always was designed to be passed an inclusive lower and an exclusive upper value for the random integer, generating a random integer that is greater than or equal to the lower value and less than the upper value specified. The MATE About application errantly subtracted 1 from the upper value itself, and thus only messages 1 through 5 were ever picked. This commit removes the unnecessary subtraction.