summaryrefslogtreecommitdiff
path: root/README.in
diff options
context:
space:
mode:
authorAlexander Larsson <alexl@redhat.com>2013-08-20 15:37:13 +0200
committerAlexander Larsson <alexl@redhat.com>2013-08-20 15:37:13 +0200
commitdd27e55a5f41000d45db1654860ca90b2240f937 (patch)
tree2b71c5ec4eddbe26f2ae09df6bd384406a4c80a6 /README.in
parent78dae73a303bd339299a7f2b04844dabb0efb401 (diff)
downloadgtk+-dd27e55a5f41000d45db1654860ca90b2240f937.tar.gz
Update README.in
Diffstat (limited to 'README.in')
-rw-r--r--README.in19
1 files changed, 19 insertions, 0 deletions
diff --git a/README.in b/README.in
index 876716536d..e64f8772df 100644
--- a/README.in
+++ b/README.in
@@ -97,6 +97,25 @@ Release notes for 3.10
to just the insensitive and backdrop states. This mostly affects
theming.
+* The way widget drawing happens has changed. Earlier versions handled
+ one expose event per GdkWindow, each with a separate cairo_t. Now we
+ only handle the expose event on the toplevel and reuse the same
+ cairo_t (with the right translation and clipping) for the entire
+ widget hierarchy, recursing down via the GtkWidget::draw signal.
+ Having all rendering in the same call tree allows effects like
+ opacity and offscreen rendering of entire widget sub-hierarchies.
+ Generally this should not require any changes in widgets, but
+ code looking at e.g. the current expose event may see different
+ behavior than before.
+
+* The Gtk+ scrolling implementation has changed. gdk_window_scroll()
+ and gdk_window_move_region() no longer copy the region on the
+ window, but rather invalidate the entire scrolled region. This is
+ slightly slower, but allowed us to implement a offscreen surface
+ scrolling method which better fits modern hardware. Most scrolling
+ widgets in Gtk+ have been converted to use this model for scrolling,
+ but external widgets implementing scrolling using GdkWindow may see
+ some slowdown.
Release notes for 3.8
=====================