Add serial argument to _gdk_windowing_got_event

[~andy/gtk] / README

diff --git a/README b/README
index ec7d5b2652a53ab19859bf0b8fd782032c85d7df..260361a02b8a58c6a43a207d7716398feca8fae9 100644 (file)
--- a/README
+++ b/README
@@ -1,7 +1,7 @@
 General Information
 ===================
 
 General Information
 ===================
 

-This is GTK+ version 2.13.7. GTK+ is a multi-platform toolkit for
+This is GTK+ version 2.16.0. GTK+ is a multi-platform toolkit for

 creating graphical user interfaces. Offering a complete set of widgets,
 GTK+ is suitable for projects ranging from small one-off projects to
 complete application suites.
 creating graphical user interfaces. Offering a complete set of widgets,
 GTK+ is suitable for projects ranging from small one-off projects to
 complete application suites.


@@ -48,6 +48,12 @@ Release notes for 2.14
   to GTK_SENSITIVITY_ON, so that the button is always sensitive or
   GTK_SENSITIVITY_OFF to make it insensitive respectively.
 
   to GTK_SENSITIVITY_ON, so that the button is always sensitive or
   GTK_SENSITIVITY_OFF to make it insensitive respectively.
 

+* GtkAdjustment now enforces that values are restricted to the
+  range [lower, upper - page_size]. This has always been the documented
+  behaviour, and the recommended practice is to set page_size to 0
+  when using adjustments for simple scalar values, like in a slider
+  or spin button.
+

 * gdk-pixbuf will use GIO for mime type detection if possible. For
   this to work, shared-mime-info needs to be installed and XDG_DATA_DIRS
   set accordingly at configure time. Otherwise, gdk-pixbuf falls
 * gdk-pixbuf will use GIO for mime type detection if possible. For
   this to work, shared-mime-info needs to be installed and XDG_DATA_DIRS
   set accordingly at configure time. Otherwise, gdk-pixbuf falls


@@ -91,38 +97,38 @@ Release notes for 2.12
 * The gtk_notebook_set/get_group_id() functions were found to be insufficient
   and have been deprecated in favour of gtk_notebook_set/get_group().
 
 * The gtk_notebook_set/get_group_id() functions were found to be insufficient
   and have been deprecated in favour of gtk_notebook_set/get_group().
 

-* The move-focus signal has been moved to GtkWidget, to unify the 
-  various implementations of this signal in specific widgets. Great care 
+* The move-focus signal has been moved to GtkWidget, to unify the
+  various implementations of this signal in specific widgets. Great care

   has been taken to make sure that all code using this signal continues
   to work.
 
   has been taken to make sure that all code using this signal continues
   to work.
 

-* An unused and hardly visible GtkFrame has been removed from the menu 
-  widget hierarchy when GtkComboBox::appears-as-list style property is 
-  set. Any RC file applying a different style to any widget below the 
-  widget path "gtk-combobox-popup-window.GtkFrame" should take into 
+* An unused and hardly visible GtkFrame has been removed from the menu
+  widget hierarchy when GtkComboBox::appears-as-list style property is
+  set. Any RC file applying a different style to any widget below the
+  widget path "gtk-combobox-popup-window.GtkFrame" should take into

   account that the frame no longer exists.
 
   account that the frame no longer exists.
 

-* The external print preview application used by GtkPrintOperationPreview 
-  is now passed the print settings on the command line with the 
-  --print-settings parameter pointing to a temp file containing the 
-  settings. The preview application assumes ownership of the file and 
-  should delete it once it does not need it anymore. The --print-settings 
-  commandline option is understood by Evince 0.9.0 and newer. To use a 
-  different print preview application, change the gtk-print-preview-command 
+* The external print preview application used by GtkPrintOperationPreview
+  is now passed the print settings on the command line with the
+  --print-settings parameter pointing to a temp file containing the
+  settings. The preview application assumes ownership of the file and
+  should delete it once it does not need it anymore. The --print-settings
+  commandline option is understood by Evince 0.9.0 and newer. To use a
+  different print preview application, change the gtk-print-preview-command

   setting in your gtkrc file, e.g. gtk-print-preview-command = "ggv %f"
 
   setting in your gtkrc file, e.g. gtk-print-preview-command = "ggv %f"
 

-* GtkMenuShell is now defined as an abstract type. It was already 
-  documented as an abstract class, and there is little reason to 
+* GtkMenuShell is now defined as an abstract type. It was already
+  documented as an abstract class, and there is little reason to

   instantiate it.
 
 * The GtkTooltips struct (this is the old tooltips API) is now considered
   private. Code that used to access this struct, in particular the
   tips_data_list field, will need to change. All of the old tooltips
   API has been deprecated in favour of a new implementation and
   instantiate it.
 
 * The GtkTooltips struct (this is the old tooltips API) is now considered
   private. Code that used to access this struct, in particular the
   tips_data_list field, will need to change. All of the old tooltips
   API has been deprecated in favour of a new implementation and

-  API. This affects all of the gtk_tooltips_ functions, and functions 
+  API. This affects all of the gtk_tooltips_ functions, and functions

   which take a GtkTooltips argument, such as gtk_tool_item_set_tooltip()
   and gtk_menu_tool_button_set_arrow_tooltip().
   which take a GtkTooltips argument, such as gtk_tool_item_set_tooltip()
   and gtk_menu_tool_button_set_arrow_tooltip().

-  
+

 * The memory management of the GtkRecentManager object has been changed,
   as using the screen didn't guarantee that the singleton instance was
   correctly destroyed. The screen-related functions have been deprecated,
 * The memory management of the GtkRecentManager object has been changed,
   as using the screen didn't guarantee that the singleton instance was
   correctly destroyed. The screen-related functions have been deprecated,


@@ -130,14 +136,14 @@ Release notes for 2.12
   the gtk_recent_manager_get_default() function is guaranteed to be valid
   for the entire lifetime of an application.
 
   the gtk_recent_manager_get_default() function is guaranteed to be valid
   for the entire lifetime of an application.
 

-* A number of interfaces that have been superseded by newer interfaces for 
-  a long time have finally been deprecated. This includes 
+* A number of interfaces that have been superseded by newer interfaces for
+  a long time have finally been deprecated. This includes

   gtk_widget_ref/unref(), gtk_rc_style_ref/unref() and the old file selector.
 
 * The various coordinate systems in use in GtkTreeView widgets have
   gtk_widget_ref/unref(), gtk_rc_style_ref/unref() and the old file selector.
 
 * The various coordinate systems in use in GtkTreeView widgets have

-  been clarified in the documentation, and in the cause of doing so, 
+  been clarified in the documentation, and in the cause of doing so,

   the functions gtk_tree_view_widget_to_tree_coords() and
   the functions gtk_tree_view_widget_to_tree_coords() and

-  gtk_tree_view_tree_to_widget_coords() have been deprecated in 
+  gtk_tree_view_tree_to_widget_coords() have been deprecated in

   favour of a new family of gtk_tree_view_convert_ functions.
 
 * gtk_menu_item_remove_submenu() has been deprecated in favour of
   favour of a new family of gtk_tree_view_convert_ functions.
 
 * gtk_menu_item_remove_submenu() has been deprecated in favour of


@@ -181,14 +187,14 @@ Release notes for 2.10
   gtk_range_set_[upper/lower]_stepper_sensitivity() functions to
   prevent the arrows from being rendered insensitive.
 
   gtk_range_set_[upper/lower]_stepper_sensitivity() functions to
   prevent the arrows from being rendered insensitive.
 

-* GtkObject now uses the "floating reference" support in GObject. 
+* GtkObject now uses the "floating reference" support in GObject.

   GTK_OBJECT_IS_FLOATING() will still work, but direct checking
   GTK_OBJECT_IS_FLOATING() will still work, but direct checking

-  of the GTK_FLOATING flag will no longer detect the floating 
+  of the GTK_FLOATING flag will no longer detect the floating

   reference. Details about floating references can be found in the docs:
   http://developer.gnome.org/doc/API/2.0/gobject/gobject-The-Base-Object-Type.html#floating-ref
 
   reference. Details about floating references can be found in the docs:
   http://developer.gnome.org/doc/API/2.0/gobject/gobject-The-Base-Object-Type.html#floating-ref
 

-* Accelerators like (_F) are now stripped from labels when they are 
-  displayed in toolbars. If this is not wanted, the feature can be 
+* Accelerators like (_F) are now stripped from labels when they are
+  displayed in toolbars. If this is not wanted, the feature can be

   suppressed by inserting a Unicode control character, e.g ZWNJ.
 
 * The pixbuf theme engine can now customize expanders (in GtkTreeView
   suppressed by inserting a Unicode control character, e.g ZWNJ.
 
 * The pixbuf theme engine can now customize expanders (in GtkTreeView


@@ -201,14 +207,14 @@ Release notes for 2.10
 
 * Several new signals have been added to GtkNotebook. Care has been taken
   to choose signal names which do not collide with signals added by well-known
 
 * Several new signals have been added to GtkNotebook. Care has been taken
   to choose signal names which do not collide with signals added by well-known

-  derived classes. The names which can no longer be used for signals in 
+  derived classes. The names which can no longer be used for signals in

   objects derived from GtkNotebook are page-reordered, page-removed and
   page-added.
 
   objects derived from GtkNotebook are page-reordered, page-removed and
   page-added.
 

-* Due to the interface changes in the file chooser backend interface, 
-  the GTK+ ABI version has been bumped to 2.10.0. Third-party filesystem 
-  backends have to be ported to the new interface, other modules, such as 
-  theme engines, input method modules or pixbuf loaders have to be rebuilt 
+* Due to the interface changes in the file chooser backend interface,
+  the GTK+ ABI version has been bumped to 2.10.0. Third-party filesystem
+  backends have to be ported to the new interface, other modules, such as
+  theme engines, input method modules or pixbuf loaders have to be rebuilt

   so that they are installed in the right place for GTK+ to find them.
 
 
   so that they are installed in the right place for GTK+ to find them.
 
 


@@ -267,19 +273,19 @@ Release notes for 2.6
   a clipboard manager following the specification at
   http://www.freedesktop.org/wiki/Standards/clipboard-manager-spec
   must be running. A sample implementation of such a clipboard manager
   a clipboard manager following the specification at
   http://www.freedesktop.org/wiki/Standards/clipboard-manager-spec
   must be running. A sample implementation of such a clipboard manager

-  is available at 
+  is available at

   http://people.imendio.com/andersca/archives/clipboard-manager-0.3.tar.gz
   http://people.imendio.com/andersca/archives/clipboard-manager-0.3.tar.gz

-  Applications can use the function gdk_display_supports_clipboard_persistence() 
+  Applications can use the function gdk_display_supports_clipboard_persistence()

   to find out if clipboard persistence is available.
 
   to find out if clipboard persistence is available.
 

-* Notification on clipboard ownership changes via GdkOwnerChange events 
+* Notification on clipboard ownership changes via GdkOwnerChange events

   requires the XFIXES X extension. Applications can use the function
   gdk_display_supports_selection_notification() to find out if ownerchip
   change notification is available.
 
   requires the XFIXES X extension. Applications can use the function
   gdk_display_supports_selection_notification() to find out if ownerchip
   change notification is available.
 

-* The icon theme code in GTK+ 2.6 follows the freedesktop.org icon theme 
-  specification. Setting the XDG_DATA_DIRS environtment variable may be 
-  necessary if your icons aren't installed in the default location 
+* The icon theme code in GTK+ 2.6 follows the freedesktop.org icon theme
+  specification. Setting the XDG_DATA_DIRS environtment variable may be
+  necessary if your icons aren't installed in the default location

   /usr/share/icons.
 
 * The icon theme code in GTK+ 2.6 can make use of mmap()able cache files
   /usr/share/icons.
 
 * The icon theme code in GTK+ 2.6 can make use of mmap()able cache files


@@ -287,49 +293,49 @@ Release notes for 2.6
   gtk-update-icon-cache to generate these cache files. For further details,
   see the gtk-update-icon-cache man page or the GTK+ documentation.
 
   gtk-update-icon-cache to generate these cache files. For further details,
   see the gtk-update-icon-cache man page or the GTK+ documentation.
 

-* To reduce code size and improve efficiency, GTK+, when compiled 
-  with the GNU toolchain, has separate internal and external entry 
-  points for exported functions. The internal names, which begin with 
+* To reduce code size and improve efficiency, GTK+, when compiled
+  with the GNU toolchain, has separate internal and external entry
+  points for exported functions. The internal names, which begin with

   IA__, may be seen when debugging a GTK+ program.
 
 * The following functions have been deprecated in GTK+ 2.6:
   gdk_pango_context_set_colormap
   gtk_cell_renderer_editing_canceled
 
   IA__, may be seen when debugging a GTK+ program.
 
 * The following functions have been deprecated in GTK+ 2.6:
   gdk_pango_context_set_colormap
   gtk_cell_renderer_editing_canceled
 

-* The new GtkFileChooser widget emphasizes simplicity and thus does 
-  not provide a navigation entry by default when opening files. 
+* The new GtkFileChooser widget emphasizes simplicity and thus does
+  not provide a navigation entry by default when opening files.

   Experienced command line users will likely want to make heavy use of
   the location dialog brought up by the Control-L key shortcut.
 
 * The GTK+ libraries use an '_' prefix to indicate private symbols that
   Experienced command line users will likely want to make heavy use of
   the location dialog brought up by the Control-L key shortcut.
 
 * The GTK+ libraries use an '_' prefix to indicate private symbols that

-  must not be used by applications. On some platforms, symbols beginning 
+  must not be used by applications. On some platforms, symbols beginning

   with prefixes such as _gtk, _gdk, and _pango will be exported
   from the library, on others not. In no case can applications
   use these private symbols. In addition to that, GTK+ 2.6 makes several
   symbols private which were not in any installed header files and
   were never intended to be exported.
 
   with prefixes such as _gtk, _gdk, and _pango will be exported
   from the library, on others not. In no case can applications
   use these private symbols. In addition to that, GTK+ 2.6 makes several
   symbols private which were not in any installed header files and
   were never intended to be exported.
 

-* The gdk_pixbuf_xlib library included in the contrib/ directory 
+* The gdk_pixbuf_xlib library included in the contrib/ directory

   and the framebuffer GDK backend included in the gdk/linux-fb directory
   and the framebuffer GDK backend included in the gdk/linux-fb directory

-  of GTK+ are provided on an as-is basis and have not been tested at all. 
+  of GTK+ are provided on an as-is basis and have not been tested at all.

   No guarantees about the degree of workingness or about future
   compatibility are provided.
 
   No guarantees about the degree of workingness or about future
   compatibility are provided.
 

-* On Unix, the assumption of GLib and GTK+ by default is that filenames on 
+* On Unix, the assumption of GLib and GTK+ by default is that filenames on

   the filesystem are encoded in UTF-8 rather than the encoding of the locale;
   the GTK+ developers consider that having filenames whose interpretation
   depends on the current locale is fundamentally a bad idea.
 
   the filesystem are encoded in UTF-8 rather than the encoding of the locale;
   the GTK+ developers consider that having filenames whose interpretation
   depends on the current locale is fundamentally a bad idea.
 

-  If you have filenames encoded in the encoding of your locale, then you 
+  If you have filenames encoded in the encoding of your locale, then you

   may want to set the G_FILENAME_ENCODING environment variable:
   may want to set the G_FILENAME_ENCODING environment variable:

-  
+

    G_FILENAME_ENCODING=@locale
    export G_FILENAME_ENCODING
 
   (Earlier versions of GLib 2.x required a different environment variable
    G_FILENAME_ENCODING=@locale
    export G_FILENAME_ENCODING
 
   (Earlier versions of GLib 2.x required a different environment variable

-  setting; G_BROKEN_FILENAMES=1 to achieve the same effect; this 
+  setting; G_BROKEN_FILENAMES=1 to achieve the same effect; this

   is still supported, but G_FILENAME_ENCODING is preferred.)
   is still supported, but G_FILENAME_ENCODING is preferred.)

-  Best integration of GTK+ 2.6 with the environment is achieved by 
+  Best integration of GTK+ 2.6 with the environment is achieved by

   using a UTF-8 locale.
 
   On Windows, filenames passed to GTK+ should always be in UTF-8, as
   using a UTF-8 locale.
 
   On Windows, filenames passed to GTK+ should always be in UTF-8, as


@@ -340,7 +346,7 @@ Release notes for 2.6
 
   When compiling against GTK+ 2.6, applications intended to be
   portable to Windows must take the UTF-8 file name encoding into
 
   When compiling against GTK+ 2.6, applications intended to be
   portable to Windows must take the UTF-8 file name encoding into

-  consideration, and use the gstdio wrappers to access files whose 
+  consideration, and use the gstdio wrappers to access files whose

   names have been constructed from strings returned from GTK+ or GLib.
 
 
   names have been constructed from strings returned from GTK+ or GLib.
 
 


@@ -350,9 +356,9 @@ How to report bugs
 Bugs should be reported to the GNOME bug tracking system.
 (http://bugzilla.gnome.org, product gtk+.) You will need to create an
 account for yourself.
 Bugs should be reported to the GNOME bug tracking system.
 (http://bugzilla.gnome.org, product gtk+.) You will need to create an
 account for yourself.

-  
+

 In the bug report please include:
 In the bug report please include:

-  
+

 * Information about your system. For instance:
 
    - What operating system and version
 * Information about your system. For instance:
 
    - What operating system and version


@@ -361,12 +367,12 @@ In the bug report please include:
 
   And anything else you think is relevant.
 
 
   And anything else you think is relevant.
 

-* How to reproduce the bug. 
+* How to reproduce the bug.

 
 

-  If you can reproduce it with one of the tests or demos built with GTK+, 
-  such as demos/gtk-demo/gtk-demo, that would be most convenient. Otherwise, 
-  please include a short test program that exhibits the behavior. As a 
-  last resort, you can also provide a pointer to a larger piece of software 
+  If you can reproduce it with one of the tests or demos built with GTK+,
+  such as demos/gtk-demo/gtk-demo, that would be most convenient. Otherwise,
+  please include a short test program that exhibits the behavior. As a
+  last resort, you can also provide a pointer to a larger piece of software

   that can be downloaded.
 
 * If the bug was a crash, the exact text that was printed out when the
   that can be downloaded.
 
 * If the bug was a crash, the exact text that was printed out when the


@@ -391,5 +397,5 @@ the patch to that bug report.
 Bug reports containing patches should include the PATCH keyword in their
 keyword fields. If the patch adds to or changes the GTK+ programming
 interface, the API keyword should also be included.
 Bug reports containing patches should include the PATCH keyword in their
 keyword fields. If the patch adds to or changes the GTK+ programming
 interface, the API keyword should also be included.

-  
+

 Patches should be in unified diff form. (The -u option to GNU diff.)
 Patches should be in unified diff form. (The -u option to GNU diff.)