When the multitasking view is opened and a the keyboard shortcuts are
used to switch between workspaces, avoid showing the nudge/bump
animation on the non-primary display.
Partially address #927
Instead of relying on a magic value to know detect mouse wheel "clicks"
use the discrete events sent by Mutter.
This will avoid breaking the multitasking scroll once
xf86-input-libinput 1.2.0 lands in Ubuntu with high-resolution scroll
wheel support.
Fix a regression changing the wallpaper introduced in
4aec79ae0d
The lambda function wasn't capturing the value of "i". Instead,
"OPTIONS.length" was always used.
When the mouse pointer pressures the hot corner after activation,
trigger the action again when a given threshold is reached without
requiring to leave and enter the hot corner again.
Fix#1078
Use Meta.Barrier to implement the hot corner functionality instead of
using a Clutter.Actor.
This approach makes easier to trigger the hot corner in multi-monitor
setups and avoids capturing events accidentally.
Fix#719Fix#1054
We currently rely on Screenshot to play the shutter sound. This means
that it needs pulseaudio permissions in Flatpak and depending on the app
taking the screenshot you might not get a sound when a screenshot is
taken.
In addition, no sound was played when a screenshot was copied directly
to the clipboard.
Play the shutter sound in Gala to avoid this problems.
Allow to save screenshot to clipboard when the filename received is
empty.
Not changing the save_image_to_file to keep backward compatibility.
Fix#1137
In previous versions of GNOME Settings daemon (elementary OS <= 5),
saving to clipboard was handled by the daemon. The daemon used to
request Gala to save the screenshot in a temp path like
"/tmp/gnome-settings-daemon-screenshot-XXXX" and copied the image to
the clipboard from there.
More information: https://github.com/elementary/gala/issues/474
Now, Gala is in charge of copying to clipboard when the take screenshot
methods receive an empty filename.
This commit: Move the code from save_image to save_image_to_file.
The scaling factor can change at any point, but the WindowClone was
saving a value calculated in the constructor, creating several bugs when
scaling was changed.
Remove that pre-calculated value and use always a fresh value.
