4 This is GTK+ version @GTK_VERSION@. GTK+ is a multi-platform toolkit for
5 creating graphical user interfaces. Offering a complete set of widgets,
6 GTK+ is suitable for projects ranging from small one-off projects to
7 complete application suites.
9 GTK+ is free software and part of the GNU Project. However, the
10 licensing terms for GTK+, the GNU LGPL, allow it to be used by all
11 developers, including those developing proprietary software, without any
12 license fees or royalties.
14 The official ftp site is:
15 ftp://ftp.gtk.org/pub/gtk
17 The official web site is:
20 Information about mailing lists can be found at
21 http://www.gtk.org/mailinglists.html
27 See the file 'INSTALL'
30 Release notes for 2.20
31 ======================
33 * GtkStatusbar now has a message area (see gtk_status_bar_get_message_area)
34 which makes it easy to place additional widgets inside the statusbar
35 frame or to replace the label widgets. Previously, this was only possible
36 by accessing the innards of the statusbar widget directly. Applications
37 which are doing so may need some adjustments, since the addition of the
38 message area changed the internal widget hierarchy.
40 Release notes for 2.18
41 ======================
43 * gtk_tooltip_set_custom now accept a NULL custom_widget to unset the
44 old custom_widget. Custom_widget does not get destroyed when the
47 * JPEG2000 support is no longer enabled by default. It must be
48 explicitly turned on, by passing --with-libjasper to configure.
50 * GDK has been reworked to implement 'client-side windows'. This offers
51 exciting new possibilities, such as transformed, offscreen rendering,
52 but it breaks some long-standing assumptions that applications may
53 have about GDK windows. Setting the environment variable
54 GDK_NATIVE_WINDOWS makes GDK create a native X11 window for each
55 GDK window, which might make problematic applications work better.
57 * GTK+ calls signal (SIGPIPE, SIG_IGN) during initialization, to ignore
58 SIGPIPE signals, since these are almost never wanted in graphical
59 applications. If you do need to handle SIGPIPE for some reason, reset
60 the handler after gtk_init(), but notice that other libraries (e.g.
61 libdbus or gvfs) might do similar things.
63 Release notes for 2.16
64 ======================
66 * Password entries now display a caps-lock warning. This can be turned off
67 with the caps-lock-warning property.
69 * Various orientation-related functions have been deprecated in favour
70 of the new GtkOrientable interface: gtk_scale_button_get_orientation,
71 gtk_scale_button_set_orientation, gtk_toolbar_set_orientation.
73 * The action-proxy interaction has been changed. Widgets that operate as
74 proxies have to implement the GtkActivatable interface now. GtkActivatable
75 implementation are responsible for syncing their appearance with the
76 action and for activating the action. All GTK+ widgets that are commonly
77 used as proxies implement the GtkActivatable interface.
79 * The handling of keyboard shortcuts has been changed, to help with a
80 longstanding complaint about the way GTK+ handles multiple layouts. GTK+
81 now only uses keys from groups other than the current group if they are
82 not present in the current group.
84 Release notes for 2.14
85 ======================
87 * gtkitemfactory.h is now completely deprecated.
88 As gtkactiongroup.h and gtkstock.h no longer include the gtkitemfactory.h
89 header, this might break application using gtk_item_factory_* symbols
90 without including gtkitemfactory.h - even though this behaviour has never
91 been supported in the first place.
93 * The GtkFileSystem semi-private interface has been removed.
94 The GTK+ filechooser implementation now uses GIO directly, which has
95 rendered external filesystem implementations unnecessary. Consequently,
96 the GtkFileSystem interface is no longer available, nor the filechooser
97 will load any GtkFileSystem implementation.
99 * GtkComboBox now renders the popdown button insensitive when
100 the model is empty. Applications which want to populate the list
101 only before displaying it can set gtk_combo_box_set_button_sensitivity
102 to GTK_SENSITIVITY_ON, so that the button is always sensitive or
103 GTK_SENSITIVITY_OFF to make it insensitive respectively.
105 * In the early 2.14.x releases, GtkAdjustment was changed to enforce
106 that values are restricted to the range [lower, upper - page_size].
107 This has always been the documented behaviour, and the recommended
108 practice is to set page_size to 0 when using adjustments for simple
109 scalar values, like in a slider or spin button.
110 Due to the large number of applications that are affected by this
111 change, the behaviour has been reverted to the old behaviour in
112 2.14.3, with an explicit warning that this change will be
113 reintroduced in 2.90.
115 * gdk-pixbuf will use GIO for mime type detection if possible. For
116 this to work, shared-mime-info needs to be installed and XDG_DATA_DIRS
117 set accordingly at configure time. Otherwise, gdk-pixbuf falls
118 back to its built-in sniffing implementation.
120 Release notes for 2.12
121 ======================
123 * gtk_about_dialog_get/set_name() were deprecated in favour of
124 gtk_about_dialog_get/set_program_name(), the GtkAboutDialog now uses the
125 "program-name" property instead of the conflicting "name" property.
127 * The gdk-pixbuf tiff loader now requires libtiff 3.6.0 or later.
129 * Support for Windows 9x/ME has officially been removed. It hasn't worked
132 * The GtkTextBufferTargetInfo enumeration values have been changed from
133 G_MAXUINT-0, G_MAXUINT-1, G_MAXUINT-2, etc, to -1, -2, -3 to stay within
136 * A change in the handling of _NET_WM_USER_TIME properties on toplevel
137 windows can cause deadlock problems with window managers that are using
138 GDK for drawing decorations. In particular, metacity <= 2.18.0 is affected
139 by this. The problem has been fixed in metacity 2.18.1.
141 * Semi-private GtkTextLayout api has changed: new GtkTextLayout method
142 invalidate_cursors(), and new functions gtk_text_layout_invalidate_cursors()
143 and gtk_text_layout_cursors_changed(), which should be used in place of
144 gtk_text_layout_invalidate() and gtk_text_layout_changed() if invalidation
145 is due to marks moved or changed selection; new GtkTextLineDisplay structure
146 member. Source compatibility is preserved; binary compatibility may break
147 only if GtkTextLineDisplay structure was created on stack or as a part
148 of another structure (in particular GnomeCanvas and its clones do not need
151 * Another new signal has been added to GtkNotebook. The new signal
152 is called create-window, so this name can no longer be used for signals
153 in objects derived from GtkNotebook.
155 * The gtk_notebook_set/get_group_id() functions were found to be insufficient
156 and have been deprecated in favour of gtk_notebook_set/get_group().
158 * The move-focus signal has been moved to GtkWidget, to unify the
159 various implementations of this signal in specific widgets. Great care
160 has been taken to make sure that all code using this signal continues
163 * An unused and hardly visible GtkFrame has been removed from the menu
164 widget hierarchy when GtkComboBox::appears-as-list style property is
165 set. Any RC file applying a different style to any widget below the
166 widget path "gtk-combobox-popup-window.GtkFrame" should take into
167 account that the frame no longer exists.
169 * The external print preview application used by GtkPrintOperationPreview
170 is now passed the print settings on the command line with the
171 --print-settings parameter pointing to a temp file containing the
172 settings. The preview application assumes ownership of the file and
173 should delete it once it does not need it anymore. The --print-settings
174 commandline option is understood by Evince 0.9.0 and newer. To use a
175 different print preview application, change the gtk-print-preview-command
176 setting in your gtkrc file, e.g. gtk-print-preview-command = "ggv %f"
178 * GtkMenuShell is now defined as an abstract type. It was already
179 documented as an abstract class, and there is little reason to
182 * The GtkTooltips struct (this is the old tooltips API) is now considered
183 private. Code that used to access this struct, in particular the
184 tips_data_list field, will need to change. All of the old tooltips
185 API has been deprecated in favour of a new implementation and
186 API. This affects all of the gtk_tooltips_ functions, and functions
187 which take a GtkTooltips argument, such as gtk_tool_item_set_tooltip()
188 and gtk_menu_tool_button_set_arrow_tooltip().
190 * The memory management of the GtkRecentManager object has been changed,
191 as using the screen didn't guarantee that the singleton instance was
192 correctly destroyed. The screen-related functions have been deprecated,
193 and should not be used anymore; the GtkRecentManager instance returned by
194 the gtk_recent_manager_get_default() function is guaranteed to be valid
195 for the entire lifetime of an application.
197 * A number of interfaces that have been superseded by newer interfaces for
198 a long time have finally been deprecated. This includes
199 gtk_widget_ref/unref(), gtk_rc_style_ref/unref() and the old file selector.
201 * The various coordinate systems in use in GtkTreeView widgets have
202 been clarified in the documentation, and in the cause of doing so,
203 the functions gtk_tree_view_widget_to_tree_coords() and
204 gtk_tree_view_tree_to_widget_coords() have been deprecated in
205 favour of a new family of gtk_tree_view_convert_ functions.
207 * gtk_menu_item_remove_submenu() has been deprecated in favour of
208 gtk_menu_item_set_submenu (..., NULL).
210 * gtk_default_draw_check() has been fixed to really decrease the
211 indicator size by one pixel to ensure an odd size instead of
212 accidentially increasing it.
213 Consequently, gtk_cell_renderer_toggle_render() could be fixed to
214 not subtract 1 from the size passed to gtk_paint_option(), which
215 was just a workaround for above off-by-two for even sizes (theme
216 engines now get the real indicator size passed).
217 The default toggle size of GtkCheckMenuItem and GtkCellRendererToggle
218 has been changed to 13 to be consistent with GtkCheckButton.
219 The only visible change with default settings is that the indicator in
220 GtkCellRendererToggle has changed its size from 11 to 13 and is now
221 consistent with menus and toggle buttons.
223 * GTK+ has always required that gtk_init() (or a variant thereof) is
224 called before any other GTK+ function. Some applications call functions
225 like gtk_clipboard_get() to check if they need to call gtk_init(),
226 anyway. A change in GLib 2.14 has recently broken this unsupported
227 practise. It is worth pointing out that calling gtk_init() twice
231 Release notes for 2.10
232 ======================
234 * The hexadecimal Unicode input feature has been reworked. It no longer
235 blocks the use of the sixteen Ctrl-Shift-<hex digit> key sequences. Now
236 it only uses Ctrl-Shift-u.
238 * A memory leak in GtkStyle handling has been fixed. This may expose bugs
239 in third-party widgets which forget to call gtk_style_attach() in their
242 * Range widgets like GtkScrollbar now render their arrows insensitive
243 when the slider is at the end. Applications which react to arrow
244 clicks even if the slider is at the end may want to use the new
245 gtk_range_set_[upper/lower]_stepper_sensitivity() functions to
246 prevent the arrows from being rendered insensitive.
248 * GtkObject now uses the "floating reference" support in GObject.
249 GTK_OBJECT_IS_FLOATING() will still work, but direct checking
250 of the GTK_FLOATING flag will no longer detect the floating
251 reference. Details about floating references can be found in the docs:
252 http://developer.gnome.org/doc/API/2.0/gobject/gobject-The-Base-Object-Type.html#floating-ref
254 * Accelerators like (_F) are now stripped from labels when they are
255 displayed in toolbars. If this is not wanted, the feature can be
256 suppressed by inserting a Unicode control character, e.g ZWNJ.
258 * The pixbuf theme engine can now customize expanders (in GtkTreeView
259 and GtkExpander) and resize grips, using the new EXPANDER and
260 RESIZE_GRIP function values.
262 * Dialogs created by gtk_about_dialog_new() no longer hide automatically
263 when the user clicks close. It is the applications responsibility to
264 hide or destroy the dialog.
266 * Several new signals have been added to GtkNotebook. Care has been taken
267 to choose signal names which do not collide with signals added by well-known
268 derived classes. The names which can no longer be used for signals in
269 objects derived from GtkNotebook are page-reordered, page-removed and
272 * Due to the interface changes in the file chooser backend interface,
273 the GTK+ ABI version has been bumped to 2.10.0. Third-party filesystem
274 backends have to be ported to the new interface, other modules, such as
275 theme engines, input method modules or pixbuf loaders have to be rebuilt
276 so that they are installed in the right place for GTK+ to find them.
279 Release notes for 2.8
280 =====================
282 * GTK+ 2.8 and Pango 1.10 require the cairo library.
284 * The default theme has been renamed to "Raleigh". Existing configurations
285 specifying the "Default" theme name should still work.
287 * The GtkTreeView::enable-search property has been changed to control
288 only typeahead search, not the C-f keybinding to start an interactive
289 search. To turn off interactive searching completely, you have to
290 set GtkTreeView::search-column to -1.
292 * The restriction on using the same cell renderer in multiple columns
293 of a GtkTreeView is now more strictly enforced.
295 * In GTK+ 2.8, GtkCalendar uses nl_langinfo() (if available) to determine
296 the first day of the week. Thus, it is possible to select the first day
297 of the week independently from the language, by setting LC_TIME.
299 * In GTK+ 2.8, the gtk-update-icon-cache utility includes image data
300 in the icon caches, which will make the icon cache files larger than
301 the one produced by GTK+ 2.6. This change will reduce the memory
302 overhead of icon themes at runtime, since all GTK+ applications can
303 share the image data in memory.
305 * In 2.8, GDK emits GdkEventGrabBroken events when a keyboard or pointer
306 grab is broken. On X11, this can happen if the same application grabs
307 again, or if the window used for the grab becomes unviewable. It happens
308 more often on Win32. Applications which use grabs should pay attention
309 to these events and do the necessary cleanups when the grab is lost.
310 * The GIOChannel code for sockets on win32 has been rewritten.
311 Applications who make non-trivial use of GIOChannels on win32 should
312 be watched for possible problems.
314 * GLib 2.8 uses atomic operations to implement reference counting, thus
315 g_object_ref/unref, g_closure_ref/sink/unref and g_iochannel_ref/unref
316 can be used without locking in multithreaded applications. Note that
317 other modifications, like concurrent setting of properties still require
320 * g_convert() and related character set conversion functions have been
321 fixed to emit pending shift states and to not cache iconv descriptors
322 across multiple calls, since that is problematic for some encodings.
323 Note that these functions are not suitable for streaming conversions;
324 use g_iconv() to do streaming conversion.
327 Release notes for 2.6
328 =====================
330 * GTK+ 2.6 supports clipboard persistency. To make use of this feature,
331 a clipboard manager following the specification at
332 http://www.freedesktop.org/wiki/Standards/clipboard-manager-spec
333 must be running. A sample implementation of such a clipboard manager
335 http://people.imendio.com/andersca/archives/clipboard-manager-0.3.tar.gz
336 Applications can use the function gdk_display_supports_clipboard_persistence()
337 to find out if clipboard persistence is available.
339 * Notification on clipboard ownership changes via GdkOwnerChange events
340 requires the XFIXES X extension. Applications can use the function
341 gdk_display_supports_selection_notification() to find out if ownerchip
342 change notification is available.
344 * The icon theme code in GTK+ 2.6 follows the freedesktop.org icon theme
345 specification. Setting the XDG_DATA_DIRS environtment variable may be
346 necessary if your icons aren't installed in the default location
349 * The icon theme code in GTK+ 2.6 can make use of mmap()able cache files
350 to avoid a lot of disk searching overhead. GTK+ includes a utility named
351 gtk-update-icon-cache to generate these cache files. For further details,
352 see the gtk-update-icon-cache man page or the GTK+ documentation.
354 * To reduce code size and improve efficiency, GTK+, when compiled
355 with the GNU toolchain, has separate internal and external entry
356 points for exported functions. The internal names, which begin with
357 IA__, may be seen when debugging a GTK+ program.
359 * The following functions have been deprecated in GTK+ 2.6:
360 gdk_pango_context_set_colormap
361 gtk_cell_renderer_editing_canceled
363 * The new GtkFileChooser widget emphasizes simplicity and thus does
364 not provide a navigation entry by default when opening files.
365 Experienced command line users will likely want to make heavy use of
366 the location dialog brought up by the Control-L key shortcut.
368 * The GTK+ libraries use an '_' prefix to indicate private symbols that
369 must not be used by applications. On some platforms, symbols beginning
370 with prefixes such as _gtk, _gdk, and _pango will be exported
371 from the library, on others not. In no case can applications
372 use these private symbols. In addition to that, GTK+ 2.6 makes several
373 symbols private which were not in any installed header files and
374 were never intended to be exported.
376 * The gdk_pixbuf_xlib library included in the contrib/ directory
377 and the framebuffer GDK backend included in the gdk/linux-fb directory
378 of GTK+ are provided on an as-is basis and have not been tested at all.
379 No guarantees about the degree of workingness or about future
380 compatibility are provided.
382 * On Unix, the assumption of GLib and GTK+ by default is that filenames on
383 the filesystem are encoded in UTF-8 rather than the encoding of the locale;
384 the GTK+ developers consider that having filenames whose interpretation
385 depends on the current locale is fundamentally a bad idea.
387 If you have filenames encoded in the encoding of your locale, then you
388 may want to set the G_FILENAME_ENCODING environment variable:
390 G_FILENAME_ENCODING=@locale
391 export G_FILENAME_ENCODING
393 (Earlier versions of GLib 2.x required a different environment variable
394 setting; G_BROKEN_FILENAMES=1 to achieve the same effect; this
395 is still supported, but G_FILENAME_ENCODING is preferred.)
396 Best integration of GTK+ 2.6 with the environment is achieved by
397 using a UTF-8 locale.
399 On Windows, filenames passed to GTK+ should always be in UTF-8, as
400 in GLib 2.6. This is different than in previous versions of GTK+
401 where the system codepage was used. As in GLib, for DLL ABI
402 stability, applications built against previous versions of GTK+ will
403 use entry points providing the old semantics.
405 When compiling against GTK+ 2.6, applications intended to be
406 portable to Windows must take the UTF-8 file name encoding into
407 consideration, and use the gstdio wrappers to access files whose
408 names have been constructed from strings returned from GTK+ or GLib.
414 Bugs should be reported to the GNOME bug tracking system.
415 (http://bugzilla.gnome.org, product gtk+.) You will need to create an
416 account for yourself.
418 In the bug report please include:
420 * Information about your system. For instance:
422 - What operating system and version
424 - For Linux, what version of the C library
426 And anything else you think is relevant.
428 * How to reproduce the bug.
430 If you can reproduce it with one of the tests or demos built with GTK+,
431 such as demos/gtk-demo/gtk-demo, that would be most convenient. Otherwise,
432 please include a short test program that exhibits the behavior. As a
433 last resort, you can also provide a pointer to a larger piece of software
434 that can be downloaded.
436 * If the bug was a crash, the exact text that was printed out when the
439 * Further information such as stack traces may be useful, but is not
440 necessary. If you do send a stack trace, and the error is an X error,
441 it will be more useful if the stacktrace is produced running the test
442 program with the --sync command line option.
448 Patches should also be submitted to bugzilla.gnome.org. If the patch
449 fixes an existing bug, add the patch as an attachment to that bug
452 Otherwise, enter a new bug report that describes the patch, and attach
453 the patch to that bug report.
455 Patches should be in unified diff form. (The -up option to GNU diff.)