GitLab

It mainly contains information that is already covered in the
API docs, or is outdated, or refers to no longer existing widgets.

"n_events" went back from guint to gint.

People were requesting it and it mirrors the behavior of GdkWindow.

gcc warns if you switch on values that are not part of the enum you're
switching on. So handle those cases in the default handler by using if
statments.

PS: Someone file a bug against cups about this?

Remove workaround for entries - the general codepath should just work.

Also, I refuse to compile with -Werror, so I don't notice.

Also, I refuse to compile with -Werror

Otherwise we get an undefined gdk_pixbuf_set_option().

This path would only do anything where widget->window was not located at
widget->allocation.x/y but at a different position. This should never
happen in the real world. But if it does, GTK3 will break for you.
Better fix your widget.

We were including at least "gtkprivate.h" before.

For launch requests coming in over DBus.

When has-entry is TRUE, GtkComboBox already adds a cell renderer
for the text column, so avoid adding a second one in GtkComboBoxText.

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

Use gtk_combo_box_get_has_entry instead.

gtk_icon_view_layout(), which can resize the bin window and thus
underlying surfaces, could be called from gtk_icon_view_draw().  So
we have to make sure that layouting is done before the draw handler is
called.  We use the same construction as in tree view here, the layout
idle handler is installed with a higher priority than
GDK_PRIORITY_REDRAW and we wrap the call to gdk_window_process_updates()
in a new function that will flush the layout queue beforehand.

This patch adds a GtkComboBox:popup-fixed-width to decide if the
popup's width should be a fixed width matching the combo's allocated width.

The patch includes a kindof hack to work around treeviews currently
not supporting height-for-width geometry (for list-mode only), this
hack can be safely removed once treeviews start reporting natural
widths properly.

We must use entry-text-column explicitly to 0, since it defaults to -1.

This will likely mean that the old examples will not appear in the
tarball until they have been integrated in the new 'getting started'
docs.