summaryrefslogtreecommitdiff
path: root/README.in
diff options
context:
space:
mode:
authorMatthias Clasen <mclasen@redhat.com>2009-05-03 13:04:06 -0400
committerMatthias Clasen <mclasen@redhat.com>2009-05-03 13:04:06 -0400
commite6373738fc9c53c95e467a3681fcd3426fd94d13 (patch)
treef590ec182722637e3c797ea64337ad3d6f3896a6 /README.in
parent46bc2ec740c9c3b86fad9c373342e0851ca0bf43 (diff)
downloadgtk+-e6373738fc9c53c95e467a3681fcd3426fd94d13.tar.gz
Forward-port a GtkAdjustment compatibility fix
We reverted GtkAdjustment to its traditional behaviour wrt. to clamping in 2.14.3, but the fix was lost between 2.14 and 2.16.
Diffstat (limited to 'README.in')
-rw-r--r--README.in14
1 files changed, 9 insertions, 5 deletions
diff --git a/README.in b/README.in
index 2bc3209a91..9f8198bcdf 100644
--- a/README.in
+++ b/README.in
@@ -69,11 +69,15 @@ 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.
-* 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.
+* In the early 2.14.x releases, GtkAdjustment was changed to enforce
+ 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.
+ Due to the large number of applications that are affected by this
+ change, the behaviour has been reverted to the old behaviour in
+ 2.14.3, with an explicit warning that this change will be
+ reintroduced in 2.90.
* 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