summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
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.
2021-04-23travis: disable travis builds for ubunturaveit651-1/+1
Sadly, there is a limit for free builds at docker.com See discussion https://github.com/orgs/mate-desktop/teams/core-team/discussions/25
2021-03-29Remove shadow warnings [-Wshadow]rbuj3-11/+7
2021-03-08travis: build with mate-common-1.24.2 from reposraveit651-11/+0
2021-02-27mate-about: Use the macro _(String) instead of the macro gettext(Msgid)rbuj2-3/+3
2021-02-27Drop local macro mate_gettext(package, locale, codeset)rbuj2-16/+6
2021-02-27Remove warning -Wbad-function-castrbuj4-36/+57
2021-02-22tx: temporarily disable build for ArchLinuxraveit651-1/+1
2021-02-08g_settings_get_string always returns a newly-allocated stringrbuj2-14/+9
2021-02-02build: set GETTEXT_PACKAGE=AC_PACKAGE_NAMErbuj1-1/+1
2021-02-02tx: update resourcerbuj2-5/+13
2021-02-02mate-color-select: Do not use deprecated gtk_button_new_from_stockrbuj1-2/+7
2020-12-08update issue templateraveit651-1/+1
2020-11-19Remove USE_MATE2_MACROS from autogen.sh (legacy)rbuj1-1/+0
2020-11-18travis CI: use rolling tag for ubuntu docker imageraveit651-1/+1
2020-11-18travis CI: fix build issue of gtk-doc moduleraveit651-0/+2
2020-08-06release 1.25.0v1.25.0raveit651-0/+24
2020-08-06tx: sysnc with transifexraveit6534-263/+1795
2020-08-06tx: update resourceraveit651-36/+81
2020-08-06mate-languages: portability of localedir fallbackrbuj1-6/+13
2020-08-06a11y-keyboard: Add togglekeys-backend settingColomban Wendling1-4/+14
2020-08-06a11y-keyboard: Add ranges for togglekeys beep settingsColomban Wendling1-0/+4
2020-08-06a11y-keyboard: Add settings to control beeps used for togglekeysColomban Wendling1-0/+20
generated by cgit v1.2.1 (git 2.18.0) at 2024-11-14 19:41:23 +0000