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.12
31 ======================
33 * Functions: gtk_about_dialog_get/set_name() were deprecated in favour of
34 gtk_about_dialog_get/set_program_name(), the GtkAboutDialog now uses the
35 "program-name" property instead of the conflicting "name" property.
37 * The tiff loader now requires libtiff 3.6.0 or later.
39 * Support for Windows 9x/ME has officially been removed. It hasn't worked
42 * The GtkTextBufferTargetInfo enumeration values have been changed from
43 G_MAXUINT-0, G_MAXUINT-1, G_MAXUINT-2, etc, to -1, -2, -3 to stay within
46 * A change in the handling of _NET_WM_USER_TIME properties on toplevel
47 windows can cause deadlock problems with window managers that are using
48 GDK for drawing decorations. In particular, metacity <= 2.18.0 is affected
49 by this. The problem has been fixed in metacity 2.18.1.
51 * Semi-private GtkTextLayout api has changed: new GtkTextLayout method
52 invalidate_cursors(), and new functions gtk_text_layout_invalidate_cursors()
53 and gtk_text_layout_cursors_changed(), which should be used in place of
54 gtk_text_layout_invalidate() and gtk_text_layout_changed() if invalidation
55 is due to marks moved or changed selection; new GtkTextLineDisplay structure
56 member. Source compatibility is preserved; binary compatibility may break
57 only if GtkTextLineDisplay structure was created on stack or as a part
58 of another structure (in particular GnomeCanvas and its clones do not need
61 * Another new signal has been added to GtkNotebook. The new signal
62 is called create-window, so this name can no longer be used for signals
63 in objects derived from GtkNotebook.
65 * The move-focus signal has been moved to GtkWidget, to unify the
66 various implementations of this signal in specific widgets. Great care
67 has been taken to make sure that all code using this signal continues
70 * Removed an unused and hardly visible GtkFrame from the menu widget hierarchy
71 when GtkComboBox::appears-as-list style property is set. Any RC file
72 applying a different style to any widget below the widget path
73 "gtk-combobox-popup-window.GtkFrame" should take into account that the
74 frame no longer exists.
76 * The external print preview application used by GtkPrintOperationPreview is
77 now passed the print settings on the command line with the --print-settings
78 parameter pointing to a temp file containing the settings. The preview
79 application assumes ownership of the file and should delete it once it does
80 not need it anymore. The --print-settings commandline option is understood
81 by Evince 0.9.0 and newer. To use a different print preview application,
82 change the gtk-print-preview-command setting in your gtkrc file, e.g.
83 gtk-print-preview-command = "ggv %f"
85 * GtkMenuShell is now defined as an abstract type. It was already
86 documented as an abstract class, and there is little reason to
89 * The GtkTooltips struct (this is the old tooltips API) is now considered
90 private. Code that used to access this struct, in particular the
91 tips_data_list field, will need to change.
93 * The memory management of the GtkRecentManager object has been changed,
94 as using the screen didn't guarantee that the singleton instance was
95 correctly destroyed. The screen-related functions have been deprecated,
96 and should not be used anymore; the GtkRecentManager instance returned by
97 the gtk_recent_manager_get_default() function is guaranteed to be valid
98 for the entire lifetime of an application.
100 Release notes for 2.10
101 ======================
103 * The hexadecimal Unicode input feature has been reworked. It no longer
104 blocks the use of the sixteen Ctrl-Shift-<hex digit> key sequences. Now
105 it only uses Ctrl-Shift-u.
107 * A memory leak in GtkStyle handling has been fixed. This may expose bugs
108 in third-party widgets which forget to call gtk_style_attach() in their
111 * Range widgets like GtkScrollbar now render their arrows insensitive
112 when the slider is at the end. Applications which react to arrow
113 clicks even if the slider is at the end may want to use the new
114 gtk_range_set_[upper/lower]_stepper_sensitivity() functions to
115 prevent the arrows from being rendered insensitive.
117 * GtkObject now uses the "floating reference" support in GObject.
118 GTK_OBJECT_IS_FLOATING() will still work, but direct checking
119 of the GTK_FLOATING flag will no longer detect the floating
120 reference. Details about floating references can be found in the docs:
121 http://developer.gnome.org/doc/API/2.0/gobject/gobject-The-Base-Object-Type.html#floating-ref
123 * Accelerators like (_F) are now stripped from labels when they are
124 displayed in toolbars. If this is not wanted, the feature can be
125 suppressed by inserting a Unicode control character, e.g ZWNJ.
127 * The pixbuf theme engine can now customize expanders (in GtkTreeView
128 and GtkExpander) and resize grips, using the new EXPANDER and
129 RESIZE_GRIP function values.
131 * Dialogs created by gtk_about_dialog_new() no longer hide automatically
132 when the user clicks close. It is the applications responsibility to
133 hide or destroy the dialog.
135 * Several new signals have been added to GtkNotebook. Care has been taken
136 to choose signal names which do not collide with signals added by well-known
137 derived classes. The names which can no longer be used for signals in
138 objects derived from GtkNotebook are page-reordered, page-removed and
141 * Due to the interface changes in the file chooser backend interface,
142 the GTK+ ABI version has been bumped to 2.10.0. Third-party filesystem
143 backends have to be ported to the new interface, other modules, such as
144 theme engines, input method modules or pixbuf loaders have to be rebuilt
145 so that they are installed in the right place for GTK+ to find them.
148 Release notes for 2.8
149 =====================
151 * GTK+ 2.8 and Pango 1.10 require the cairo library.
153 * The default theme has been renamed to "Raleigh". Existing configurations
154 specifying the "Default" theme name should still work.
156 * The GtkTreeView::enable-search property has been changed to control
157 only typeahead search, not the C-f keybinding to start an interactive
158 search. To turn off interactive searching completely, you have to
159 set GtkTreeView::search-column to -1.
161 * The restriction on using the same cell renderer in multiple columns
162 of a GtkTreeView is now more strictly enforced.
164 * In GTK+ 2.8, GtkCalendar uses nl_langinfo() (if available) to determine
165 the first day of the week. Thus, it is possible to select the first day
166 of the week independently from the language, by setting LC_TIME.
168 * In GTK+ 2.8, the gtk-update-icon-cache utility includes image data
169 in the icon caches, which will make the icon cache files larger than
170 the one produced by GTK+ 2.6. This change will reduce the memory
171 overhead of icon themes at runtime, since all GTK+ applications can
172 share the image data in memory.
174 * In 2.8, GDK emits GdkEventGrabBroken events when a keyboard or pointer
175 grab is broken. On X11, this can happen if the same application grabs
176 again, or if the window used for the grab becomes unviewable. It happens
177 more often on Win32. Applications which use grabs should pay attention
178 to these events and do the necessary cleanups when the grab is lost.
179 * The GIOChannel code for sockets on win32 has been rewritten.
180 Applications who make non-trivial use of GIOChannels on win32 should
181 be watched for possible problems.
183 * GLib 2.8 uses atomic operations to implement reference counting, thus
184 g_object_ref/unref, g_closure_ref/sink/unref and g_iochannel_ref/unref
185 can be used without locking in multithreaded applications. Note that
186 other modifications, like concurrent setting of properties still require
189 * g_convert() and related character set conversion functions have been
190 fixed to emit pending shift states and to not cache iconv descriptors
191 across multiple calls, since that is problematic for some encodings.
192 Note that these functions are not suitable for streaming conversions;
193 use g_iconv() to do streaming conversion.
196 Release notes for 2.6
197 =====================
199 * GTK+ 2.6 supports clipboard persistency. To make use of this feature,
200 a clipboard manager following the specification at
201 http://www.freedesktop.org/wiki/Standards/clipboard-manager-spec
202 must be running. A sample implementation of such a clipboard manager
204 http://people.imendio.com/andersca/archives/clipboard-manager-0.3.tar.gz
205 Applications can use the function gdk_display_supports_clipboard_persistence()
206 to find out if clipboard persistence is available.
208 * Notification on clipboard ownership changes via GdkOwnerChange events
209 requires the XFIXES X extension. Applications can use the function
210 gdk_display_supports_selection_notification() to find out if ownerchip
211 change notification is available.
213 * The icon theme code in GTK+ 2.6 follows the freedesktop.org icon theme
214 specification. Setting the XDG_DATA_DIRS environtment variable may be
215 necessary if your icons aren't installed in the default location
218 * The icon theme code in GTK+ 2.6 can make use of mmap()able cache files
219 to avoid a lot of disk searching overhead. GTK+ includes a utility named
220 gtk-update-icon-cache to generate these cache files. For further details,
221 see the gtk-update-icon-cache man page or the GTK+ documentation.
223 * To reduce code size and improve efficiency, GTK+, when compiled
224 with the GNU toolchain, has separate internal and external entry
225 points for exported functions. The internal names, which begin with
226 IA__, may be seen when debugging a GTK+ program.
228 * The following functions have been deprecated in GTK+ 2.6:
229 gdk_pango_context_set_colormap
230 gtk_cell_renderer_editing_canceled
232 * The new GtkFileChooser widget emphasizes simplicity and thus does
233 not provide a navigation entry by default when opening files.
234 Experienced command line users will likely want to make heavy use of
235 the location dialog brought up by the Control-L key shortcut.
237 * The GTK+ libraries use an '_' prefix to indicate private symbols that
238 must not be used by applications. On some platforms, symbols beginning
239 with prefixes such as _gtk, _gdk, and _pango will be exported
240 from the library, on others not. In no case can applications
241 use these private symbols. In addition to that, GTK+ 2.6 makes several
242 symbols private which were not in any installed header files and
243 were never intended to be exported.
245 * The gdk_pixbuf_xlib library included in the contrib/ directory
246 and the framebuffer GDK backend included in the gdk/linux-fb directory
247 of GTK+ are provided on an as-is basis and have not been tested at all.
248 No guarantees about the degree of workingness or about future
249 compatibility are provided.
251 * On Unix, the assumption of GLib and GTK+ by default is that filenames on
252 the filesystem are encoded in UTF-8 rather than the encoding of the locale;
253 the GTK+ developers consider that having filenames whose interpretation
254 depends on the current locale is fundamentally a bad idea.
256 If you have filenames encoded in the encoding of your locale, then you
257 may want to set the G_FILENAME_ENCODING environment variable:
259 G_FILENAME_ENCODING=@locale
260 export G_FILENAME_ENCODING
262 (Earlier versions of GLib 2.x required a different environment variable
263 setting; G_BROKEN_FILENAMES=1 to achieve the same effect; this
264 is still supported, but G_FILENAME_ENCODING is preferred.)
265 Best integration of GTK+ 2.6 with the environment is achieved by
266 using a UTF-8 locale.
268 On Windows, filenames passed to GTK+ should always be in UTF-8, as
269 in GLib 2.6. This is different than in previous versions of GTK+
270 where the system codepage was used. As in GLib, for DLL ABI
271 stability, applications built against previous versions of GTK+ will
272 use entry points providing the old semantics.
274 When compiling against GTK+ 2.6, applications intended to be
275 portable to Windows must take the UTF-8 file name encoding into
276 consideration, and use the gstdio wrappers to access files whose
277 names have been constructed from strings returned from GTK+ or GLib.
283 Bugs should be reported to the GNOME bug tracking system.
284 (http://bugzilla.gnome.org, product gtk+.) You will need to create an
285 account for yourself.
287 In the bug report please include:
289 * Information about your system. For instance:
291 - What operating system and version
293 - For Linux, what version of the C library
295 And anything else you think is relevant.
297 * How to reproduce the bug.
299 If you can reproduce it with one of the tests or demos built with GTK+,
300 such as demos/gtk-demo/gtk-demo, that would be most convenient. Otherwise,
301 please include a short test program that exhibits the behavior. As a
302 last resort, you can also provide a pointer to a larger piece of software
303 that can be downloaded.
305 * If the bug was a crash, the exact text that was printed out when the
308 * Further information such as stack traces may be useful, but is not
309 necessary. If you do send a stack trace, and the error is an X error,
310 it will be more useful if the stacktrace is produced running the test
311 program with the --sync command line option.
317 Patches should also be submitted to bugzilla.gnome.org. If the patch
318 fixes an existing bug, add the patch as an attachment to that bug
321 Otherwise, enter a new bug report that describes the patch, and attach
322 the patch to that bug report.
324 Bug reports containing patches should include the PATCH keyword in their
325 keyword fields. If the patch adds to or changes the GTK+ programming
326 interface, the API keyword should also be included.
328 Patches should be in unified diff form. (The -u option to GNU diff.)