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

*** empty log message ***

Browse Source
This commit is contained in:
Owen Taylor
2001-07-22 21:03:03 +00:00
parent f4ca329027
commit 5f50d1fd72
2 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
docs/reference/ChangeLog
View File

@ -1,3 +1,8 @@
Sun Jul 22 17:01:34 2001 Owen Taylor <otaylor@redhat.com>
* gtk/tmpl/gtksignal.sgml: Fix missing not
(Skip Montanaro, #56361)
Wed Jul 4 22:53:33 2001 Owen Taylor <otaylor@redhat.com> Wed Jul 4 22:53:33 2001 Owen Taylor <otaylor@redhat.com>
* gtk/tmpl/gtkplug.sgml gtk/tmpl/gtksocket.sgml: Some * gtk/tmpl/gtkplug.sgml gtk/tmpl/gtksocket.sgml: Some

2
docs/reference/gtk/tmpl/gtksignal.sgml
View File

@ -31,7 +31,7 @@ from being run.)
</para> </para>
<para> <para>
Signals are used by everyone, but they are only Signals are used by everyone, but they are only
created on a per class basis-- so you should call created on a per class basis-- so you should not call
call gtk_signal_new() unless you are writing call gtk_signal_new() unless you are writing
a new #GtkObject type. However, if you want to make a new signal a new #GtkObject type. However, if you want to make a new signal
for an existing type, you may use gtk_object_class_user_signal_new() for an existing type, you may use gtk_object_class_user_signal_new()