| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
*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
|
|
*put XKillClient and gdk_x11_screen_get_xscreen behind x11-only runtime checks
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
The timestamp is compared with g_file_info_get_attribute_uint64
in mate_desktop_item_get_file_status (const MateDesktopItem *item)
|
|
The timestamp is retrieved with g_file_info_get_attribute_uint64
in get_mtime (const char *filename)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
mate_minor_version and mate_micro_version always 1. In addition, mate_minor / mate_minor_version and mate_micro / mate_micro_version always same.
|
|
closes https://github.com/mate-desktop/mate-desktop/issues/475
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
fixes build issues with fedora:latest (f34) tag.
|
|
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.
|
|
Sadly, there is a limit for free builds at docker.com
See discussion
https://github.com/orgs/mate-desktop/teams/core-team/discussions/25
|
|
|
