From a3bdc2c334cc79f3ce2f0796702dcd030d27d3c0 Mon Sep 17 00:00:00 2001 From: Christophe Fergeau Date: Wed, 3 Nov 2004 18:49:59 +0000 Subject: [PATCH] docs/random/signal: added notes about using BOXED for GstBuffer signal marshallers, not POINTER Original commit message from CVS: 2004-11-03 Christophe Fergeau * docs/random/signal: added notes about using BOXED for GstBuffer signal marshallers, not POINTER --- ChangeLog | 5 +++++ docs/random/signal | 12 ++++++++++++ 2 files changed, 17 insertions(+) create mode 100644 docs/random/signal diff --git a/ChangeLog b/ChangeLog index 541f3fef98..4ab79f50db 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2004-11-03 Christophe Fergeau + + * docs/random/signal: added notes about using BOXED for GstBuffer + signal marshallers, not POINTER + 2004-11-03 Christophe Fergeau * gst/elements/gstfakesink.c: (gst_fakesink_class_init): diff --git a/docs/random/signal b/docs/random/signal new file mode 100644 index 0000000000..679a36c122 --- /dev/null +++ b/docs/random/signal @@ -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