interesting
/
libui
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

More stuff in lifetimes.md.

This commit is contained in:
Pietro Gagliardi 2015-04-19 22:10:11 -04:00
parent d181acc10e
commit 91522894c1
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/lifetimes.md
View File

@ -32,7 +32,7 @@ Note that control implementations generally don't need to worry about backend-sp
Windows has no reference counting for window handles. The only situations where a window handle can be destroyed are Windows has no reference counting for window handles. The only situations where a window handle can be destroyed are
- with a call to `DestroyWindow()`, or - with a call to `DestroyWindow()`, or
- by `DefWindowProc()` if it receives a `WM_CLOSE` message - by `DefWindowProc()` if it receives a `WM_CLOSE` message (when the user clicks the Close button on the titlebar of a toplevel window, for instance)
The destruction process is simple: The destruction process is simple:
@ -53,6 +53,8 @@ What does this mean? In the normal case, you create a widget, add it to a contai
Note that removing a widget from a container does not call `gtk_widget_destroy()`; it merely decrements the reference count of the widget. Note that removing a widget from a container does not call `gtk_widget_destroy()`; it merely decrements the reference count of the widget.
As with Windows, a `::delete-event` signal (which is sent when the user clicks a toplevel window's Close button) that is allowed to propagate will result in the window being destroyed.
TODO describe what we need to do TODO describe what we need to do
TODO remove lifetimes.c? TODO remove lifetimes.c?