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

Explain that unmap-event may never be emitted

Browse Source 
Fixes: https://bugzilla.gnome.org/show_bug.cgi?id=613302
This commit is contained in:
Christian Dywan 2010-05-21 17:10:25 +02:00
parent 280b01a8db
commit 82e27aede9
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
gtk/gtkwidget.c
View File

@ -1576,9 +1576,13 @@ gtk_widget_class_init (GtkWidgetClass *klass)
* @widget: the object which received the signal
* @event: the #GdkEventAny which triggered this signal
*
* The ::unmap-event signal will be emitted when the @widget's window is
* The ::unmap-event signal may be emitted when the @widget's window is
* unmapped. A window is unmapped when it becomes invisible on the screen.
*
* For performance reasons GTK+ may not emit ::unmap-event, so one
* should always also implement ::unrealize in order to release
* resources and disconnect signal handlers.
*
* To receive this signal, the #GdkWindow associated to the widget needs
* to enable the #GDK_STRUCTURE_MASK mask. GDK will enable this mask
* automatically for all new windows.