From 1030d9e5b12e880e55f6bd3184dc6f3646be2e19 Mon Sep 17 00:00:00 2001 From: Matthias Clasen Date: Wed, 18 Jul 2018 20:22:18 -0400 Subject: [PATCH] docs: Small updates to the migration guide Mention that event controllers are available in 3.x, amongst others. --- docs/reference/gtk/migrating-3to4.xml | 21 ++++++++++++++------- 1 file changed, 14 insertions(+), 7 deletions(-) diff --git a/docs/reference/gtk/migrating-3to4.xml b/docs/reference/gtk/migrating-3to4.xml index 7ed61f9dfb..40c0dde97f 100644 --- a/docs/reference/gtk/migrating-3to4.xml +++ b/docs/reference/gtk/migrating-3to4.xml @@ -20,11 +20,11 @@ The steps outlined in the following sections assume that your - application is working with GTK+ 3.22, which is the final stable + application is working with GTK+ 3.24, which is the final stable release of GTK+ 3.x. It includes all the necessary APIs and tools to help you port your application to GTK+ 4. If you are still using an older version of GTK+ 3.x, you should first get your application - to build and work with the latest minor release in the 3.22 series. + to build and work with the latest minor release in the 3.24 series.
@@ -34,7 +34,7 @@ widgets have been deprecated. These deprecations are clearly spelled out in the API reference, with hints about the recommended replacements. The API reference for GTK+ 3 also includes an - index of all deprecated symbols. + index of all deprecated symbols. To verify that your program does not use any deprecated symbols, @@ -79,13 +79,13 @@ Review your window creation flags GTK+ 4 removes the GDK_WA_CURSOR flag. Instead, just use - gdk_surface_set_cursor() to set a cursor on the window after + gdk_window_set_cursor() to set a cursor on the window after creating it. GTK+ 4 also removes the GDK_WA_VISUAL flag, and always uses an RGBA visual for windows. To prepare your code for this, - use gdk_surface_set_visual (gdk_screen_get_rgba_visual ()) after + use gdk_window_set_visual (gdk_screen_get_rgba_visual ()) after creating your window. @@ -169,6 +169,14 @@
+
+ Stop using GtkWidget event signals + + Event controllers and #GtkGestures replace event signals in GTK+ 4. They + have been backported to GTK+ 3.x so you can prepare for this change. + +
+
@@ -432,8 +440,7 @@ GtkWidget event signals are removed Event controllers and #GtkGestures have already been introduced in GTK+ 3 to handle - input for many cases. In GTK+ 4, even more are available, such as #GtkEventControllerScroll - and GtkEventControllerMotion, and the traditional widget signals for handling input, + input for many cases. In GTK+ 4, the traditional widget signals for handling input, such as #GtkWidget::motion-event or #GtkWidget::event have been removed.