GitLab

This adds specific marshallers for all of the locations where a generic
marshaller is being used. It also provides va_marshallers to reduce the
chances that we get stack traces from perf going through ffi_call_unix64.

This is forward ported from gtk-3-24.

# Conflicts:
#	gtk/gtkeventcontrollerkey.c
#	gtk/gtkeventcontrollermotion.c
#	gtk/gtkgesture.c
#	gtk/gtkgesturemultipress.c

Remove all the old 2.x and 3.x version annotations.
GTK+ 4 is a new start, and from the perspective of a
GTK+ 4 developer all these APIs have been around since
the beginning.

To some extent, pad and touchpad gesture events need extra API.

This avoids pointless allocations

We let these through in GtkEventController::filter, and handle
these especially on GtkGesture::update.

This prevents some of our generic object implementation tests
from working with gesture objects. Instead, add g_return_if_fail
checks in all the gesture constructors.

Whether the gesture is active or recognized should be checked before in
callers, or just not used naively.

Matthias Clasen authored May 05, 2014 and Carlos Garnacho committed May 23, 2014

For now, at least. We do this by hiding the instance and
class structures in private headers.

This gesture implementation recognizes rotations when fed with
events from two different GdkEventSequences