[gtk/ebassi/docs-for-master: 1/3] docs: Mention Window::close-request in the migration guide




commit 078ada75d46ada778b29bc1f94a105c40631c810
Author: Emmanuele Bassi <ebassi gnome org>
Date:   Wed Jun 9 18:03:12 2021 +0100

    docs: Mention Window::close-request in the migration guide
    
    The Widget::delete-event signal was moved to Window::close-request.

 docs/reference/gtk/migrating-3to4.md | 15 ++++++++++-----
 1 file changed, 10 insertions(+), 5 deletions(-)
---
diff --git a/docs/reference/gtk/migrating-3to4.md b/docs/reference/gtk/migrating-3to4.md
index 9bc982962a..49f3d6c8dd 100644
--- a/docs/reference/gtk/migrating-3to4.md
+++ b/docs/reference/gtk/migrating-3to4.md
@@ -187,11 +187,16 @@ for this change.
 | ::grab-broken-event | - |
 
 Event signals which are not directly related to input have to be dealt with
-on a one-by-one basis. If you were using `::configure-event` and
-`::window-state-event` to save window state, you should use property
-notification for corresponding [class@Gtk.Window] properties, such as
-[property@Gtk.Window:default-width], [property@Gtk.Window:default-height],
-[property@Gtk.Window:maximized] or [property@Gtk.Window:fullscreened].
+on a one-by-one basis:
+
+ - If you were using `::configure-event` and `::window-state-event` to save
+   window state, you should use property notification for corresponding
+   [class@Gtk.Window] properties, such as [property@Gtk.Window:default-width],
+   [property@Gtk.Window:default-height], [property@Gtk.Window:maximized] or
+   [property@Gtk.Window:fullscreened].
+ - If you were using `::delete-event` to present a confirmation when using
+   the close button of a window, you should use the
+   [signal@Gtk.Window::close-request] signal.
 
 ### Set a proper application ID
 


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]