AuroraMiddleware/gtk2
1
0
Fork 0
forked from AuroraMiddleware/gtk
Code Issues Pull Requests Projects Releases Wiki Activity

docs: Add some more to the migration guide

Browse Source 
Expand the section on life-cycle handling with some
more details.
This commit is contained in:
Matthias Clasen 2020-10-21 14:30:17 -04:00
parent 3151906157
commit d7794bf608
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/reference/gtk/migrating-3to4.md
View File

@ -264,6 +264,14 @@ therefore can no longer be used to break reference cycles. A typical sign
of a reference cycle involving a toplevel window is when closing the window of a reference cycle involving a toplevel window is when closing the window
does not make the application quit. does not make the application quit.
A good rule to follow is: If you set a widget pointer with
gtk_widget_class_bind_template_child() in class_init(), you need to
unparent it in dispose(). The slight complication here is that you need
to respect the widget hierarchy while doing so. Ie if you set both `field1`
and `field2`, but `field1` is an ancestor of `field2`, then you only need
to unparent `field1` — doing so will remove the the entire subtree below
`field1`, including `field2`.
### Stop using GdkScreen ### Stop using GdkScreen
The GdkScreen object has been removed in GTK 4. Most of its APIs already The GdkScreen object has been removed in GTK 4. Most of its APIs already