ff4d87727b
Update license access method
...
Dropped obsolete Free Software Foundation address pointing
to the FSF website instead as suggested by
https://www.gnu.org/licenses/gpl-howto.html
keeping intact the important part of the historical notice
as requested by the license.
Resolving rpmlint reported issue E: incorrect-fsf-address.
Signed-off-by: Sandro Bonazzola <sbonazzo@redhat.com >
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3155 >
2023-08-30 08:48:23 +02:00
d1d2496c99
core: Replace MetaVirtualModifier
...
By making all the types uses ClutterModifierType instead.
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2407 >
2022-12-22 15:13:54 +01:00
7e9d9c7eb9
core: Add meta_accelerator_name
...
As we have switched to using meta_parse_accelerator in PadActionMapper.
We need a function that does the other direction for the client side
usage. See
https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/f1d50a4a/js/ui/padOsd.js#L107
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2407 >
2022-12-22 15:13:54 +01:00
2f4a68c8c3
Clean up include macros mess
...
The order and way include macros were structured was chaotic, with no
real common thread between files. Try to tidy up the mess with some
common scheme, to make things look less messy.
2018-11-06 17:17:36 +01:00
e160babe3f
keybindings: Avoid using unitialized memory and grabbing random keys
...
meta_parse_accelerator() considers 0 length accelerator strings as
valid, meaning that the keybinding should be disabled. Unfortunately,
it doesn't initialize the MetaKeyCombo so if the caller doesn't
initialize it either, we end up using random values and possibly
grabbing random keys.
https://bugzilla.gnome.org/show_bug.cgi?id=766270
2016-05-12 20:06:02 +02:00
4d80a4cc31
Use more g_autofoo throughout mutter
2015-05-29 17:18:35 -07:00
13acf9e35d
keybindings: Have meta_accelerator_parse take a MetaKeyCombo
2015-01-06 19:11:57 -08:00
8d29d22e99
meta_accelerator_parse(): handle keysyms without the XF86 prefix
...
The GDK and hence GNOME standard is that keys that begin with XF86 according to
libxkbcommon not prefixed with XF86, though gdk_keyval_from_name() strips XF86
if provided. If libxkbcommon doesn't recognize the accelerator name without
XF86, try again adding XF86 to the start.
This restores compatibility with gnome-settings-daemon, schemas, and existing
user configuration.
https://bugzilla.gnome.org/show_bug.cgi?id=727993
2014-06-27 10:37:42 -04:00
e04e9aac39
Fix an uninitialized variable warning
2014-04-22 21:09:06 -04:00
a7d4713393
accel-parse: Add a notice about where the code came from
2014-04-07 11:25:16 -04:00
4d4ecae2a1
accel-parse: Clean up trailing whitespace
2014-04-07 11:24:23 -04:00
545c3b6678
accel-parse: Clean up error handling
...
Now that we have the code in-tree, we can change the API to actually
report an error rather than checking afterwards.
2014-04-07 11:21:36 -04:00
e70f336a09
accel-parse: Use libxkbcommon for keysym parsing
...
This kills our dependency on GTK+ / GDK entirely.
2014-04-07 11:19:41 -04:00
806f1742ac
accel-parse: Switch code to output MetaVirtualModifier directly
2014-04-07 11:19:40 -04:00
0dc63f395d
accel-parse: Remove support for <Release>
2014-04-07 11:15:01 -04:00
616f1a09b1
accel-parse: Add keycode parsing as well
2014-04-07 11:15:01 -04:00
50e69109b6
accel-parse: Integrate Above_Tab parsing code directly into our copy
2014-04-07 11:15:01 -04:00
242784d3e4
accel-parse: Copy the code from GTK+ in-tree
...
We can't use GTK+ for accelerator parsing under Wayland, since we
don't want to go through Xwayland to make that happen.
2014-04-07 11:14:35 -04:00
0466fe9301
Move meta_ui_parse_accelerator into core/
...
We're currently using GTK+ for this, but we'll stop doing that fairly
quickly and instead just copy the GTK+ code in-tree.
2014-04-07 10:59:46 -04:00
