docs/random/signal: added notes about using BOXED for GstBuffer signal marshallers, not POINTER

Original commit message from CVS:
2004-11-03  Christophe Fergeau  <teuf@gnome.org>

* docs/random/signal: added notes about using BOXED for GstBuffer
signal marshallers, not POINTER
This commit is contained in:
Christophe Fergeau 2004-11-03 18:49:59 +00:00
parent 074dc0340c
commit a3bdc2c334
2 changed files with 17 additions and 0 deletions

View file

@ -1,3 +1,8 @@
2004-11-03 Christophe Fergeau <teuf@gnome.org>
* docs/random/signal: added notes about using BOXED for GstBuffer
signal marshallers, not POINTER
2004-11-03 Christophe Fergeau <teuf@gnome.org> 2004-11-03 Christophe Fergeau <teuf@gnome.org>
* gst/elements/gstfakesink.c: (gst_fakesink_class_init): * gst/elements/gstfakesink.c: (gst_fakesink_class_init):

12
docs/random/signal Normal file
View file

@ -0,0 +1,12 @@
Random notes on signals:
* Use a BOXED (and not a POINTER) marshaller when your signal will have a
GstBuffer argument:
g_signal_new ("handoff", G_TYPE_FROM_CLASS (klass), G_SIGNAL_RUN_LAST,
G_STRUCT_OFFSET (GstIdentityClass, handoff), NULL, NULL,
gst_marshal_VOID__BOXED, G_TYPE_NONE, 1,
GST_TYPE_BUFFER | G_SIGNAL_TYPE_STATIC_SCOPE);
* For GstBuffers arguments, consider using G_SIGNAL_TYPE_STATIC_SCOPE as it
can prevent an extra copy of the buffer