callisto-debian/gtk2
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Reword explanation of delete-event and destroy

Browse Source
This commit is contained in:
Christian Dywan
2010-03-12 21:03:35 +01:00
parent 325c86f83c
commit 072673c612
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/tutorial/gtk-tut.sgml
View File

@ -822,11 +822,11 @@ until we call gtk_widget_show(window) near the end of our program.</para>
</programlisting> </programlisting>
<para>Here are two examples of connecting a signal handler to an object, in <para>Here are two examples of connecting a signal handler to an object, in
this case, the window. Here, the "delete_event" and "destroy" signals this case, the window. Here, the "delete-event" and "destroy" signals
are caught. The first is emitted when we use the window manager to are caught. The first is emitted when we use the window manager to
kill the window, or when we use the gtk_widget_destroy() call passing kill the window. The second is emitted when we use the gtk_widget_destroy() call
in the window widget as the object to destroy. The second is emitted passing in the window widget as the object to destroy, or when, in the
when, in the "delete_event" handler, we return FALSE. "delete-event" handler, we return FALSE.
The <literal>G_CALLBACK</literal> is a macro The <literal>G_CALLBACK</literal> is a macro
that performs type casting and checking for us, as well as aid the readability of that performs type casting and checking for us, as well as aid the readability of