Make sure to save the style context before querying
with other states. This stops GTK+ from warning, and
makes things work.

When the current submenu in a GtkPopoverMenu is selected, and we
are editing its submenu child property, we get change notification
for the popovers visible-submenu property. Don't clear the selection
in this case because the visible submenu did not actually change
to a different widget, it just changed its name.

There is no embed widget in the ui file, so don't refer to one.

The dispose code was throwing away the list of properties
without clearing out the quick-access hash table, so getters
could still return already-freed property objects. This
was causing the popover code to crash.

GtkPopover was introduced in 3.12, GtkPopoverMenu and GtkModelButton
are coming in 3.16.

Disable the ::icon and ::iconic properties until there
is a proper editor for GIcons.

It belongs to the other buttons, so move it there.

This should serve as the final proof that you don't let your
developers draw icons...

It doesn't make sense to allow this.

This change makes glade create a popover when the user clicks
on the button in the palette, which is the expected behavior.

With respect to visibility, popovers should be treated like
toplevels: It takes an explicit action to show them.

Deal with 'spontaneous' changes of the visible submenu. This will
happen once we add model buttons.

Ensure that the submenu containing the currently selected widget is
visible.

Add GtkPopoverMenu with two virtual properties, one for the number
of menus, and one for the currently edited menu.

Makes more sense there.

This is pretty bare-bones at the moment.

https://bugzilla.gnome.org/show_bug.cgi?id=740104

Patch by Juan Pablo Ugarte

Anders Jonsson authored Dec 15, 2014 and Matthias Clasen committed Dec 01, 2015

https://bugzilla.gnome.org/show_bug.cgi?id=741552

This is a new addition to the GdkEventMask enum.

https://bugzilla.gnome.org/show_bug.cgi?id=758287

Some of these have appeared in the last year or so.

https://bugzilla.gnome.org/show_bug.cgi?id=758288

This value was added to the GtkInputHints enum in 3.18.

https://bugzilla.gnome.org/show_bug.cgi?id=758289

This value has been added to the GtkPolicyType enum in 3.16.

https://bugzilla.gnome.org/show_bug.cgi?id=758290

GtkAction has been deprecated since GTK 3.10, so this commit marks it deprecated
and moves the widgets into the 'Deprecated' section.  This also deprecates all
the GtkActivatable properties (e.g. look at the properties of a GtkButton in
glade).

https://bugzilla.gnome.org/show_bug.cgi?id=757609

GTK+ warns nowadays if the state passed to gtk_style_context_get_*
does not match the state of the context. Avoid this by setting
the state beforehand.

https://bugzilla.gnome.org/show_bug.cgi?id=758300

GTK+ warns nowadays if the state passed to gtk_style_context_get_*
does not match the state of the context. Avoid this by setting
the state beforehand. This is just a bandaid fix; the drawing
should be redone in terms of gtk_render_ APIs instead of poking
at colors.

https://bugzilla.gnome.org/show_bug.cgi?id=758299

GTK+ warns nowadays if the state passed to gtk_style_context_get_*
does not match the state of the context. Avoid this by using the
state of the context.

https://bugzilla.gnome.org/show_bug.cgi?id=758297

GTK+ warns nowadays if the state passed to gtk_style_context_get_*
does not match the state of the context. Avoid this by setting
the state beforehand. This is just a bandaid fix; the drawing
should be redone in terms of gtk_render_ APIs instead of poking
at colors.

https://bugzilla.gnome.org/show_bug.cgi?id=758296

These have no effect anymore, other than causing warnings.

https://bugzilla.gnome.org/show_bug.cgi?id=758280