And make sure it's included everywhere it's needed.

Don't call a useless function, call gtk_widget_set_child_visible()
directly.

Also, add docs for the model property while I'm looking at the file.

Refactor the child allocation machinery, so that the complex allocation
paths are only run when the animation is running.

And in particular, ensure that when no animation is running, the
identity transform is allocated.

... and add a property for it.

Renderers don't need a display until they get realized. And once they
get realized, they can look up the display from the surface.

The signature of the enter/leave signals changed.
Adapt all users.

Oops

paned: Don't use a grab

See merge request !644

motion controller: add details to signals

See merge request !621

gdk: Include copy of glib/gconstructor.h

See merge request !642

It does not seem necessary for proper functioning
of the drag handle.

When dealing with subclasses of GtkEntry, we were not
getting the property offset that is stored on the GtkEntry
type.

This was showing up as criticals when trying to set
::width-chars on a GtkFileChooserEntry.

This is named gdkconstructor.h to avoid any possible conflicts. This fixes
the current usages of G_HAS_CONSTRUCTORS, as that header is not installed
by glib.

This information can be needed in signal handlers,
so make it available.

Add boolean properties, is-pointer-focus and
contains-pointer-focus, that track whether the pointer
is in the widget itself or in one of its descendants.

The ::enter and ::leave signals get emitted up and down the
connecting path between the old an the new pointer location.

The signals are less useful if you can't find out where along
the path you are. That is what crossing mode and detail are
about, so add those to the signals.

This was relying on setting has-focus for initial focus.

Move focus to GtkRoot

See merge request !640

It does not exist anymore. I'm removing this code now
because our CI tests are using xim and fail due to this.

Eventually, this code should be ported to use a popover.

The changes here are all related to initial focus.

Check that we get the expected sequences of focus
change events for the nonlinear, inferior and ancestor
cases.

It would be nice to do the same checks for crossing
events, but we have no gtk_window_set_hover().

It doesn't really make sense to have only
the setter, but not the getter public.

A bunch of API was missing here.

We now set current_event for focus-change as well,
so make sure to check the event type.

Mention the limitations of the key forwarding api.

This information can be needed in signal handlers,
so make it available.

Add boolean properties, is-focus and contains-focus, that
track whether the focus is in the widget itself or in
one of its descendants.

Prefix the finalize function properly.

This information is useful when maintaining a
'last focus' field.

Update all users.

Put this code in the same place where we generate
the crossing events.

In the inferior and ancestor cases, we were missing
the initial/final event.

Emit focus change events in the same way as crossing events.
Also change the code to only emit focus change events for
the master keyboard - we only maintain a single focus location,
so sending multiple focus change events for different devices
seems confusing.

We want to use this for focus changes, now that
it can emit focus change events.