This Week in GTK+ – 4

In this last week, GTK+ has seen 55 commits, with 2378 lines added and 1493 lines removed.

Planning and Status
  • Carlos Soriano has been working on further experiments on the new path bar widget in various topic branches.
  • Emmanuele Bassi has been working on a new API for simplifying the drawing entry points inside GtkWidget, in preparation for the new rendering API inside GSK.
Notable changes
  • Timm Bäder added an accessible representation for GtkStack to only show the current visible child in accessibility tools.
  • Matthias Clasen added a warning in case we emit the GtkWidget::draw call on a widget without an allocation; this is not supposed to happen, and a warning allows tracking badly behaving widgets.
  • Lapo Calamandrei fixed Adwaita with regards to menu items, info bars, and the caret color of selectable lables.
  • Matthias Clasen deprecated the GtkSizeGroup:ignore-hidden property, and documented it as broken; sizing of invisible widgets is not really possible, as they lack access to windowing system and style resources. It is recommended to use a GtkStack, instead, to reserve space for hidden widgets.
  • A new GDK device source type, GDK_SOURCE_TRACKPOINT, has been added to represent Trackpoint/point stick pointing devices; this new device type can be used to implement device-specific behavior in widgets.
  • CSS text styling properties can now be used on the value and marks of a GtkScale and GtkProgressbar widgets.
  • Georges Basile Stavracas Neto implemented the max-content-width and max-content-height properties in GtkScrolledWindow; Tristan Van Berkom fixed long-standing sizing issues with the existing min-content-width and min-content-height properties.
Bugs fixed
  • Bug 745622 Selected text not highlighted in GtkInfoBar
  • Bug 767058 GtkInfoBar: right-click/context menu all white
  • Bug 767052 Wayland: Iconifying a modal dialog makes the app unusable
  • Bug 767100 Add an input source type for trackpoints
  • Bug 767108 Separators not correctly placed in GtkPopover
  • Bug 767093 wayland: Provide information about scroll devices
  • Bug 753202 change cursor for click scrolling
  • Bug 767165 Update docs for availability of GDK_GRAB_FAILED
  • Bug 742281 GtkScrolledWindow should have max-content-height and max-content-width properties
  • Bug 674215 regression with updating tooltips
  • Bug 556254 Test properties of type GObject in the ‘object’ test
  • Bug 708148 gtk_tree_view_get_path_at_pos mistakenly identifies column of initial pixels
  • Bug 765595 Modal popover does not close when focus leaves it
  • Bug 766569 Better size requisition for GTK_SCROLL_NATURAL children
  • Bug 767238 Fix long standing regression in min-content-width/min-content-height
Get Involved

Interested in working on GTK+? Look at the list of bugs for newcomers and join the IRC channel #gtk+ on

This Week in GTK+ – 3

In this last week, GTK+ has seen 26 commits, with 5081 lines added and 3618 lines removed.

Planning and Status
Notable changes
  • The documentation has seen various improvements, notably in the CSS reference and the GTK+ 2.x → 3.x migration guide.
  • Matthias Clasen added a section to the API reference that maps the release notes in the README file; this section will be used as the starting point for the migration guide from 3.x to future major releases of GTK+.
  • The gtk-builder-tool utility, which allows to validate, simplify, preview, or inspect a UI description file now leaves the GtkDialog:border-width property alone when simplifying the properties set to a default value.
Bugs fixed
  • Bug 759037 GtkInfoBar: documentation not updated wrt background colors and message types
  • Bug 747206 gtktextview: note on how to get line spacing between two paragraphs
  • Bug 766643 Frozen windows when unmapped with pending configure event
  • Bug 766122 Re-used filechooser displays $pwd half of the time when shown
  • Bug 766878 placesview: Do not mark icon name as translatable
  • Bug 764203 Default background color for the ‘textview border’ node
Get Involved

Interested in working on GTK+? Look at the list of bugs for newcomers and join the IRC channel #gtk+ on

This Week in GTK+ – 2

In this last week, GTK+ has seen 90 commits, with 8502 lines added and 7914 lines removed.

Planning and Status
  • Matthias Clasen updated the GTK+ road map entry for a “tab strip” GtkStack controller widget with his prototype branch.
Notable changes
  • Matthias Clasen and Lapo Calamandrei commited some CSS changes to GtkScale that were required in order to cover all possible cases of marks on all sides. Additionally, the value node GtkScale uses when it displays a value was missing from the documentation, and has now been added.
  • Debarshi Ray fixed some allocation issues with GTK_POLICY_NEVER in GtkScrolledWindow discovered while working on libvte.
  • Matthias Clasen added two new cursor names, context-menu and no-drop, to the list of CSS cursor names supported by GTK; the cursors are provided by Adwaita.
  • Matthew Waters fixed GDK to use the thread-safe Wayland dispatch API; this is especially useful in case multiple threads are polling the Wayland file descriptor.
  • Olivier Fourdan worked on allowing the Wayland backend to try and return sensible values when asking GDK on which monitor a window is displayed; this is still a work in progress, and may require protocol extensions to avoid guesswork that can lead to false positives.
  • Ondrej Holy worked on GIO, GVFS, and GTK+ to ensure that cold-plugged drives would be appropriately detected as removable in the side bar for the file selection dialog.
  • Javier Jardón finally updated GTK+ to use upstream gettext, instead of the macro and build files modified by GLib.
Bugs fixed
  • Bug 373745 Do not use AM_GLIB_DEFINE_LOCALEDIR(GTK_LOCALEDIR) and use gettext instead
  • Bug 766405 Stack shows incorrect frame in widget factory on wayland
  • Bug 763852 gdk/wayland: event source is not multi-thread aware
  • Bug 766314 Spurious leave-notify event after touch up
  • Bug 766442 Broken drag & drop between windows
  • Bug 766440 Scale slider button has stopped discerning & rendering appropriately for scales with vs without marks
  • Bug 766566 Wayland: gdk_screen_get_monitor_at_window() unreliable under Wayland
  • Bug 766336 Crash when selecting rows with rubberbanding
  • Bug 765924 Improve external drives detection
  • Bug 766642 Switches in HeaderBars Are Badly Integrated
  • Bug 766737 stack: Only map children when necessary
  • Bug 766323 GTKPopover gives warnings if visible when reparented
  • Bug 766782 OpenGL in broadway leads to segmentation fault
Get Involved

Interested in working on GTK+? Look at the list of bugs for newcomers and join the IRC channel #gtk+ on

Cursors in GTK+


Cursors have traditionally been a big mess in Linux.

The X11 cursor font has been passed down to us from times immemorial, and given us gems such as gumby () or trek (). Unfortunately for us, this state of affairs was frozen into the GDK api with the GdkCursorType enumeration and the gdk_cursor_new() function.

Later on, the Xcursor library came around. It invented its own image format for storing cursors and brought us cursor themes, but didn’t do anything to answer the question “What cursors should my cursor theme provide ?”

Since there is no official list of recommended cursor names, cursor themes frequently provide all the variants of cursor names that have been spotted in the wild. As an example, here is the list of cursors included in the oxygen cursor theme. If you are wondering, the hex strings in this list are a clever trick of Xcursor to retrofit themed cursors underneath core X11 applications that use cursors from the cursor font mentioned above.

CSS to the rescue

About a year ago, we decided to finally improve the GTK+ cursor story. Thankfully, the CSS3 spec contains a decent list of cursor names that can be reasonably expected to be available across platforms.

Standard cursorsSince the GdkCursorType enumeration contains too much nonsense and is not easily extensible, we decided to make gdk_cursor_new_from_name() the recommended API for obtaining cursors. The documentation for this function now lists the CSS cursor names (follow the link above to see it), and the cursor handling code in the various GDK backends tries hard to give you meaningful cursors for all of these names.

On some platforms (such as X11 with a random cursor theme), we may have to fall back to the default arrow cursor if a certain cursor is not present in the theme. As part of this general overhaul of the cursor code, the Windows backend grew support for cursor themes.

GTK+ itself is now using gdk_cursor_new_from_name() exclusively, with the standard cursor names. And gtk3-demo includes a demo that shows all the standard cursors and lets you try them out. The screenshot above shows it.

The changes described here went into GTK+ 3.18, which was released about 9 months ago.

What you should do in your application

Most likely, you don’t have to do anything! GTK+ widgets use suitable cursors all by themselves, and you can benefit from that without any extra work.

If your application is creating its own cursors for whatever reason, you should check carefully if one of the standard cursors shown above is suitable for you. Using a standard cursor ensures that you will get a suitable cursor regardless of the platform your application is running on and regardless of the cursor theme the user has chosen.

Please use gdk_cursor_new_from_name() to generate your themed cursor, since this is now the preferred API for this task.

This Week in GTK+ – 1

What’s up with GTK+ for the week of 9 May 2016 – 15 May 2016

In this last week, GTK+ has seen 51 commits, with 5375 lines added and 4970 lines removed.

Planning and Status

The 3.22 development cycle is picking up pace while we go through the items of the Roadmap.

Notable changes
  • Olivier Fourdan fixed scroll event handling in GtkMenu, to ensure that it behaves consistently on X11 and Wayland with regards to smooth and discrete scrolling
  • The list of available protocols in the Connect to Server help popover is now populated using the list of supported schemes in GVFS, thanks to Georges Basile Stavracas Neto
  • Benjamin Otte has pushed a commit that lets GtkWidget emit the style-updated signal on unrealized widgets instead of delaying until realization; the original behavior was the result of an older optimization to avoid too many invalidations during construction, but the style system has improved over the years.
  • Timm Bäder pushed various clean up commits over various widgets, like GtkListBox, GtkStack, and GtkToolbar.
Bugs fixed
  • Bug 766166 key bindings in gtk.css are ignored
  • Bug 766207 Fix build on pre-C99 compilers
  • Bug 765939 [Wayland] very slow scrolling in GtkMenu using the touchpad
  • Bug 756570 gtkplacesview no longer provides guidance on address formats
  • Bug 766120 Scale draw_value() align changed from centre/right (H/V) to left, causing significant visual regression
  • Bug 766233 Crash when server does not support XI2
  • Bug 766175 Translation of quotes may misinterpreted by GTK sidebar
  • Bug 765700 GtkPaned use causes “How does the code know the size to allocate?”
  • Bug 682080 Gtk:ERROR:gtktoolbar.c:2271:logical_to_physical: assertion failed: (logical == 0)
  • Bug 766458 widget: fix GtkLabelAccessible NULL links.
Get Involved

Interested in working on GTK+? Look at the list of bugs for newcomers and join the IRC channel #gtk+ on

This Week in GTK – 0

In order to improve the communication between the GTK team and the rest of the GNOME platform, as well as application developers, we’re going to start writing weekly status reports on what happens in GTK and the rest of the core GNOME platform.

These reports are heavily inspired by the ones that the Servo team writes.

You can expect a weekly post on this blog every Monday; we’ll look at notable changes; new contributors; new features or deprecations; and scheduled events.

If you have questions, as usual, direct them to the GTK development mailing list.

Have fun!

Hello, World! (Reprise)

Hi all, and welcome back to the GTK+ development blog.

We’ve neglected this blog for a while, after the 3.0 release, but we think it’s kind of important to have a place where to talk about GTK+ (and the rest of the core GNOME platform), how it’s changing, and where it’s going.

Going forward, we are not going to use this blog for announcements — though if you want the, you can simply subscribe to the gnome-announcement mailing list. Instead, we are going to use this space to present what is happening in GTK+; to discuss the road map; to spotlight some new feature, and maybe some old one that is not well known.

Stay tuned, and as usual: have fun!

Newly designed now up and running!

Originally, the website for was going to be updated in line with the release for GTK+ 3.0 but there were a few set backs and more review needed. Finally, it’s up and running thanks to a lot of help from Devin Samarin and comments from the GTK+ community.

We have more plans to improve things on the website such as business support around GTK+ which is not really obvious enough on the current website. As part of the updates to the new website, we now list more recently established maintainers of the toolkit (seen on the Development page).

GTK+ 2.20 Released

GTK+ 2.20 adds new functionality while maintaining source and binary compatibility with GTK+ 2.18. Highlights of new features and improvements in GTK+ 2.20 are:

Noteworthy changes:

  • GtkSpinner, GtkCellRendererSpinner – A new widget that renders a ‘spinner’ animation to indicate ongoing activity. The corresponding cell renderer renders the same animation inside a treeview
  • GtkOffscreenWindow – A new toplevel container widget to manage offscreen rendering of child widgets
  • GtkNotebook – You can now show ‘action widgets’ in the space that is not occupied by tabs. This functionality is also available in GtkBuilder via the ‘action-start’ and ‘action-end’ child types.
  • Filechooser – GtkFileSystemModel has been reimplemented, for major speedup and simplifications.
  • Keyboard handling – The compose sequences understood by the builtin input method have been synced with, and the additional sequences have been rationalized
  • Mnemonic underlines – Can now optionally be hidden until the Alt key is pressed, this can be turned on with the gtk-auto-mnemonics setting
  • Keyboard accelerators – The Super, Meta and Hyper modifiers are working more reliably
  • GDK – There is a new function to get the ‘primary’ monitor in multi-monitor setups: gdk_screen_get_primary_monitory.
  • gdk-pixbuf – Embedded color profiles in png and tiff images can be stored and retrieved. Support for the QTIF image format has been added
  • Win32 – XP themes have been disabled since they don’t work
  • OS X – GTK+ uses standard Mac keyboard shortcuts (Cmd-X/Cmd-C instead of Ctrl-X/Ctrl-C, etc). The handling of multi-monitor setups has been greatly improved
  • Introspection support – Introspection data is now included in GTK+ itself. As a consequence, a dependency on gobject-introspection has been added

GLib 2.24.0 released

GLib 2.22 is a stable release adding an incremental improvement in functionality over GLib 2.20 while maintaining binary and source compatibility. Major changes include:

  • The requirements for g_thread_init() have been relaxed slightly, it can be called multiple times, and does not have to be the first call. GObject now links to GThread and threads are enabled automatically when g_type_init() is called. Thread-safety issuesvwith boxed types in GObject have been fixed. The -pthread flag has been added to all gmodule .pc files, because it is not generally permissible to load modules that are linked against libpthread if the program has not been compiled with threading support.
  • GType now has a G_DEFINE_INTERFACE convenience macro
  • GIO supports lazy loading of GIO modules, and there is a new gio-querymodule utility that goes along with this. Packagers will need to adapt to this.
  • GIO uses splice(2) to transfer data between file descriptors without extraneous copies.
  • The GVariant variant datatype has been added.