In this last week, the master branch of GTK+ has seen 40 commits, with 1551 lines added and 1998 lines removed.
Planning and status
- Matthias Clasen released the first GTK+ 3.89 development snapshot
- The GTK+ road map is available on the wiki.
Notable changes
On the master branch:
- Andrew Chadwick landed a series of fixes for graphic tablets support on Windows
- Benjamin Otte removed the
gtk_cairo_should_draw_window()
utility function; the function was introduced for compatibility in the 3.x API, but now it’s not necessary any more - Benjamin also removed
gdk_window_process_updates()
andgdk_window_process_all_updates()
; GDK has long since been switched to a frame clock; additionally, only top levelGdkWindow
can be used as a rendering surface - Lapo Calamandrei updated the High Contrast and Adwaita theme with the recent round of CSS improvements for progress bars and gradients
Bugs fixed
- 774114 – Window shadows are repainted even if only the contents of the window change
- 774695 – GtkProgressbar needs full and empty classes
- 774265 – No tilt for wintab devices
- 774699 – [wintab, potential segfault]: list iteration regression causes odd-indexed devices to be ignored during lookup & e.g. present no pressure
- 775038 – Build: Add wayland to GSKs dependencies
- 774917 – [wayland] child subsurfaces need to be placed relative to their parent
- 774893 – Application font sizes scaling gets clamped to 1.00 when starting GtkInspector
- 774939 – GtkLabelAccessible: Initialize link before setting parent
- 774760 – inspector: ensure controller is a GtkGesture
- 774686 – GtkMenu does not unref all GtkCheckMenuItem it creates
- 774743 – GtkNotebook does not unref all GtkBuiltinIcon it creates
- 774790 – GtkTextHandle does not unref all GtkAdjustment it references
Getting involved
Interested in working on GTK+? Look at the list of bugs for newcomers and join the IRC channel #gtk+ on irc.gnome.org.
Is there any plan to fix this 15 year old Gtk bug:
http://bugzilla.gnome.org/show_bug.cgi?id=85715
Is it particularly hard to fix ?
This bug hits emacs users a lot…
Thank you!