Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

No functional changes, prep work for an upcoming patch.

This reverts commit 6893f59a.

This is a new type of events, see
https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/72



For axis events of source wheel/tilt it effectively replaces the existing
axis/axis_discrete events in favour of a value based on 1 wheel detent ==
value 120. This allows for finer-grained scrolling on HW that supports those
devices - 4 events of 30 for example.

Those events should be assumed to be a separate event stream from the same
device which means we will (likely, depends on the compositor's backwards
compatibility requirements) get both legacy and new hires wheel events. Where
a frame is a pure legacy frame the axis_v120 value is zero so we know we can
ignore the rest.

Our code ends up as:
- source finger/continuous - no changes
- source wheel:
  - handle nonzero v120 events as smooth scroll events and pass them through
    accordingly
  - handle zero v120 events by throwing away axis data from this frame
  - handle axis/discrete without a v120 event as we did previously

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>

imwayland: Clamp the surrounding string end correctly

Closes #2565

See merge request GNOME/gtk!1621

Focus test

See merge request GNOME/gtk!1622

In the paths where len > MAX_LEN and cursor/anchor are separated by
at least MAX_LEN from text edges, we were clamping the right end of
the surrounding string at MAX_LEN. Oops.

This end anchor may go as far as the string length, although just
up to len - MAX_LEN in real terms (due to the condition above that
caches cursor/anchor positions being near enough the text end).

Closes: GNOME/gtk#2565

(cherry-picked from commit d7fb15c8)

It is hard to avoid widgets with the same name in a
large ui file - try harder to record a full focus chain
before decide that we've wrapped, by including the widget
address in the comparison. Note that we don't include
the addresses in the generated output, since that would
make expected output vary from run to run.

Annotation fixes

See merge request GNOME/gtk!1616

gdk: Move GdkGrabStatus and GdkGrabOwnership decl.

See merge request GNOME/gtk!1615

Match the arguments name in the declaration and the definition, and make
sure we have the proper transfer annotations.

With the removal of `gdk_seat_grab` we do not need to keep the
definitions of `GdkGrabStatus` and `GdkGrabOwnership` public.

Move those definitions to become internal only.

Matthiasc/for master

See merge request GNOME/gtk!1611

Clarify a point that took me a few hours to fully track
down, so lets preserve what I found for the next poor
sould coming this way.

Entries and menubuttons are no longer focusable themselves,
they have focusable children. Since we don't have accessible
objects for those, transfer the focus-related state (focusable
and focused) from the children to the main accessible object.

We don't get a focus-out on the event controller, when
the surface is losing keyboard focus, since we are not
moving our focus to some other widget, so we are never
unsetting the mnemonics-visible property. Do that in
response to surface state changes instead.

gdk/wayland: Clear modifiers when we lose keyboard focus

Closes #2112

See merge request GNOME/gtk!1610

Jan Alexander Steffens authored Apr 02, 2020 and Matthias Clasen committed Apr 02, 2020

When we `Alt+Tab` away from a GTK application, it loses keyboard focus.
If we don't clear the modifiers, events from other devices that we
receive while unfocused will assume `Alt` is still pressed. This results
in e.g. Firefox navigating through the history instead of scrolling the
page when using the mouse wheel on it.

We don't get any information about modifiers while we are missing
keyboard focus, so assuming no modifiers are active is the best we can
do.

The shell sends us a modifier update immediately before we regain
keyboard focus, so the state shouldn't get out of sync.

Fixes GNOME/gtk#2112

supp: Use a single suppressions file for lib, lib64 and multiarch

See merge request GNOME/gtk!1603

Im context wayland fixes

See merge request GNOME/gtk!1605

This ensures that it is done only once.

We are not loading the Compose file for individual contexts,
it just gets added to a global list. So don't pass an im context
along. This will let us move the loading out of the initialization
of individual contexts, and only do it once.

There is nothing display-specific in the ~/.Compose file,
so we can just try to load it without looking at the
display we are on.

We are loading a file here, thankfully in a thread, but
we do it every time an entry is created. Add a profiler
mark, to make this visible.

In addition to the traditional library directory lib and the 64-bit
multilib directory lib64, this will cover Debian-style multiarch
(lib/x86_64-linux-gnu etc.), Arch Linux 32-bit (lib32), x32 and
various others.

Signed-off-by: Simon McVittie <smcv@debian.org>

Fix crossing event generation

Closes #2536

See merge request GNOME/gtk!1601

We were not properly setting the new_descendent field
in Crossing structs for GTK_CROSSING_OUT events. This
was causing extraneous ::leave signals to be emitted,
and make model buttons in popover menus flicker when
hovered.

Fixes: GNOME/gtk#2536

gtk-demo: Remove the popover demo

Closes #2429

See merge request GNOME/gtk!1600

It doesn't work anymore, since popovers now need
support in the parent, and we don't really need
a demo just for popovers. They are used everywhere
already.

Fixes: GNOME/gtk#2429

gtkflowbox: Fix a minor typo in the documentation

See merge request GNOME/gtk!1599

Signed-off-by: Philip Withnall <withnall@endlessm.com>

keynav: Fix Shift-Tab

See merge request GNOME/gtk!1598

Add a cursor-aspect-ratio setting

See merge request GNOME/gtk!1597

This was broken by the shortcuts branch merge.

Add a setting that controls how thick the text caret is drawn.
The default value is 0.04.