GitLab

This is not used anymore.

This is not used anymore.

Reviewing the existing settings, the only backend with
some differences in the modifier intent settings is OS X,
and we would rather have that implemented by interpreting
the existing modifiers in the appropriate way.

                X11      Wayland  Win32    OS X

primary         ctrl     ctrl     ctrl     mod2
mnemonic        alt      alt      alt      alt
context menu    -        -        -        ctrl
extend sel      shift    shift    shift    shift
modify sel      ctrl     ctrl     ctrl     mod2
no text         alt|ctrl alt|ctrl alt|ctrl mod2|ctrl
shift group     varies   -        -        alt

GTK now uses the following modifiers:

primary         ctrl
mnemonic        alt
extend sel      shift
modify sel      ctrl
no text         alt|ctrl

The context menu and shift group intents were not used
in GTK at all.

Update tests to no longer expect <Primary> to roundtrip
through the accelerator parsing and formatting code.

These are not used anymore.

Drop the vfuncs and their implementations in the
broadway, x11, wayland and win32 backends as well.

We have replacement apis in GdkDevice and GdkDisplay.

This code needs to be redone differently, since keymaps are no
longer going to be exposed. There should really not be this much
ifdef-ed backend-specific code here anyway. Or any, really.

Remove MOD2..MOD5. Backends are expected to just set
the named modifiers.

Add all of the keyboard translation results in the key event,
so we can translate the keyboard state at the time the event
is created, and avoid doing state translation at match time.

We actually need to carry two sets of translation results,
since we ignore CapsLock when matching accelerators, in
gdk_event_matches().

At the same time, drop the scancode field - it is only ever
set on win32, and is basically unused in GTK.

Update all callers.

These are going away. We expect to just have
named modifiers in modifier masks now, so we
longer juggle 'real' and 'virtual' modifiers.

These are going away in the GdkModifierType cleanup.
Just compare the modifiers we got.

These are going away in the GdkModifierType cleanup.

The win32 backend is using GDK_MOD2_MASK for AltGr,
so define GDK_MOD2_MASK locally to keep this working,
but remove any mention of GDK_MOD3_MASK,...,GDK_MOD5_MASK.

These are going away in the GdkModifierType cleanup.

This really has no purpose and obscures the header.

These are never used in practice, and we never want to
see them in the UI, so stop supporting them. This is
in preparation for cleaning up GdkModifierType.

We've hardcoded Mod1 = Alt for a long time, there is
no need to keep the confusing naming around anymore.

This is not doing anything useful here.

This removes the last uses of GdkKeymap from GTK.

Stop using most keymap apis in GTK. Only a few calls
related to virtual modifiers are left.

We want to stop exposing GdkKeymap, so this
functionality needs a new home.

We are going to use this type in a different header.

GdkKeymap is on the way out.

GdkKeymap is on the way out.

Show the caps lock warning regardless of whether we
have the peek icon or not.

This is a counterpart to gdk_event_matches() that can
be used to obtain a shortcut matching an event.

Move the elaborate key event matching code from
GtkShortcutTrigger to GdkEvent, which greatly reduces
the amount of keymap api use outside of GDK.

Matthiasc/for master

See merge request !1630

Using the assistant demo repeatedly was crashing.

shortcuts: documentation fixes

See merge request !1628

shortcuts: documentation fixes

See merge request !1628

Update symbol lists, and add examples for parsing triggers
and actions.

Matthiasc/for master

See merge request !1626

The color swatch in the button does not need a
context menu. Turn it off.

The colorbutton contains a button which contains a colorswatch.
We want the focus to go straight to the button, nowhere else,
so mark the swatch as !can-focus.

Adapt tests to match.