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 irc.gnome.org.

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 irc.gnome.org.

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 irc.gnome.org.

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 irc.gnome.org.

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!