mirrors/gstreamer
mirrors/gstreamer
1
1
Fork 0
mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2024-12-23 00:36:51 +00:00
Code Issues 1 Projects Releases Wiki Activity
gstreamer/doc/en/Gst.GLib/SignalCallback.xml

313 lines
11 KiB
XML
Raw Normal View History

Use internal glib-sharp copy everywhere and make it work side-by-side with real glib-sharp glib-sharp will only get a new release with the new API that we need for 3.0 in a year or something. Instead of waiting a year before we can release something we now have our own internal copy of glib-sharp trunk that will be dropped once glib-sharp 3.0 is released. Everything is now compilable and working without any additional patches.
2009-08-05 14:57:20 +00:00
<Type Name="SignalCallback" FullName="Gst.GLib.SignalCallback">
<TypeSignature Language="C#" Value="public abstract class SignalCallback : IDisposable" />
<AssemblyInfo>
<AssemblyName>gstreamer-sharp</AssemblyName>
<AssemblyVersion>0.9.0.0</AssemblyVersion>
Update docs
2009-09-11 08:11:19 +00:00
<AssemblyVersion>0.9.1.0</AssemblyVersion>
Update docs
2009-10-02 13:50:16 +00:00
<AssemblyVersion>0.9.2.0</AssemblyVersion>
Update API to 0.10.25.2
2010-02-01 09:44:21 +00:00
<AssemblyVersion>0.9.3.0</AssemblyVersion>
Use internal glib-sharp copy everywhere and make it work side-by-side with real glib-sharp glib-sharp will only get a new release with the new API that we need for 3.0 in a year or something. Instead of waiting a year before we can release something we now have our own internal copy of glib-sharp trunk that will be dropped once glib-sharp 3.0 is released. Everything is now compilable and working without any additional patches.
2009-08-05 14:57:20 +00:00
</AssemblyInfo>
<Base>
<BaseTypeName>System.Object</BaseTypeName>
</Base>
<Interfaces>
<Interface>
<InterfaceName>System.IDisposable</InterfaceName>
</Interface>
</Interfaces>
<Attributes>
<Attribute>
Update docs
2009-09-16 06:41:09 +00:00
<AttributeName>System.Obsolete("Replaced by Gst.GLib.Signal.")</AttributeName>
Use internal glib-sharp copy everywhere and make it work side-by-side with real glib-sharp glib-sharp will only get a new release with the new API that we need for 3.0 in a year or something. Instead of waiting a year before we can release something we now have our own internal copy of glib-sharp trunk that will be dropped once glib-sharp 3.0 is released. Everything is now compilable and working without any additional patches.
2009-08-05 14:57:20 +00:00
</Attribute>
</Attributes>
<Docs>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
<Members>
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="protected SignalCallback (Gst.GLib.Object obj, Delegate eh, Type argstype);" />
<MemberType>Constructor</MemberType>
<AssemblyInfo>
<AssemblyVersion>0.9.0.0</AssemblyVersion>
Update docs
2009-09-11 08:11:19 +00:00
<AssemblyVersion>0.9.1.0</AssemblyVersion>
Update docs
2009-10-02 13:50:16 +00:00
<AssemblyVersion>0.9.2.0</AssemblyVersion>
Update API to 0.10.25.2
2010-02-01 09:44:21 +00:00
<AssemblyVersion>0.9.3.0</AssemblyVersion>
Use internal glib-sharp copy everywhere and make it work side-by-side with real glib-sharp glib-sharp will only get a new release with the new API that we need for 3.0 in a year or something. Instead of waiting a year before we can release something we now have our own internal copy of glib-sharp trunk that will be dropped once glib-sharp 3.0 is released. Everything is now compilable and working without any additional patches.
2009-08-05 14:57:20 +00:00
</AssemblyInfo>
<Parameters>
<Parameter Name="obj" Type="Gst.GLib.Object" />
<Parameter Name="eh" Type="System.Delegate" />
<Parameter Name="argstype" Type="System.Type" />
</Parameters>
<Docs>
<param name="obj">To be added.</param>
<param name="eh">To be added.</param>
<param name="argstype">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="_argstype">
<MemberSignature Language="C#" Value="protected Type _argstype;" />
<MemberType>Field</MemberType>
<AssemblyInfo>
<AssemblyVersion>0.9.0.0</AssemblyVersion>
Update docs
2009-09-11 08:11:19 +00:00
<AssemblyVersion>0.9.1.0</AssemblyVersion>
Update docs
2009-10-02 13:50:16 +00:00
<AssemblyVersion>0.9.2.0</AssemblyVersion>
Update API to 0.10.25.2
2010-02-01 09:44:21 +00:00
<AssemblyVersion>0.9.3.0</AssemblyVersion>
Use internal glib-sharp copy everywhere and make it work side-by-side with real glib-sharp glib-sharp will only get a new release with the new API that we need for 3.0 in a year or something. Instead of waiting a year before we can release something we now have our own internal copy of glib-sharp trunk that will be dropped once glib-sharp 3.0 is released. Everything is now compilable and working without any additional patches.
2009-08-05 14:57:20 +00:00
</AssemblyInfo>
<ReturnValue>
<ReturnType>System.Type</ReturnType>
</ReturnValue>
<Docs>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="_handler">
<MemberSignature Language="C#" Value="protected Delegate _handler;" />
<MemberType>Field</MemberType>
<AssemblyInfo>
<AssemblyVersion>0.9.0.0</AssemblyVersion>
Update docs
2009-09-11 08:11:19 +00:00
<AssemblyVersion>0.9.1.0</AssemblyVersion>
Update docs
2009-10-02 13:50:16 +00:00
<AssemblyVersion>0.9.2.0</AssemblyVersion>
Update API to 0.10.25.2
2010-02-01 09:44:21 +00:00
<AssemblyVersion>0.9.3.0</AssemblyVersion>
Use internal glib-sharp copy everywhere and make it work side-by-side with real glib-sharp glib-sharp will only get a new release with the new API that we need for 3.0 in a year or something. Instead of waiting a year before we can release something we now have our own internal copy of glib-sharp trunk that will be dropped once glib-sharp 3.0 is released. Everything is now compilable and working without any additional patches.
2009-08-05 14:57:20 +00:00
</AssemblyInfo>
<ReturnValue>
<ReturnType>System.Delegate</ReturnType>
</ReturnValue>
<Docs>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="_HandlerID">
<MemberSignature Language="C#" Value="protected uint _HandlerID;" />
<MemberType>Field</MemberType>
<AssemblyInfo>
<AssemblyVersion>0.9.0.0</AssemblyVersion>
Update docs
2009-09-11 08:11:19 +00:00
<AssemblyVersion>0.9.1.0</AssemblyVersion>
Update docs
2009-10-02 13:50:16 +00:00
<AssemblyVersion>0.9.2.0</AssemblyVersion>
Update API to 0.10.25.2
2010-02-01 09:44:21 +00:00
<AssemblyVersion>0.9.3.0</AssemblyVersion>
Use internal glib-sharp copy everywhere and make it work side-by-side with real glib-sharp glib-sharp will only get a new release with the new API that we need for 3.0 in a year or something. Instead of waiting a year before we can release something we now have our own internal copy of glib-sharp trunk that will be dropped once glib-sharp 3.0 is released. Everything is now compilable and working without any additional patches.
2009-08-05 14:57:20 +00:00
</AssemblyInfo>
<ReturnValue>
<ReturnType>System.UInt32</ReturnType>
</ReturnValue>
<Docs>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="_Instances">
<MemberSignature Language="C#" Value="protected static System.Collections.Hashtable _Instances;" />
<MemberType>Field</MemberType>
<AssemblyInfo>
<AssemblyVersion>0.9.0.0</AssemblyVersion>
Update docs
2009-09-11 08:11:19 +00:00
<AssemblyVersion>0.9.1.0</AssemblyVersion>
Update docs
2009-10-02 13:50:16 +00:00
<AssemblyVersion>0.9.2.0</AssemblyVersion>
Update API to 0.10.25.2
2010-02-01 09:44:21 +00:00
<AssemblyVersion>0.9.3.0</AssemblyVersion>
Use internal glib-sharp copy everywhere and make it work side-by-side with real glib-sharp glib-sharp will only get a new release with the new API that we need for 3.0 in a year or something. Instead of waiting a year before we can release something we now have our own internal copy of glib-sharp trunk that will be dropped once glib-sharp 3.0 is released. Everything is now compilable and working without any additional patches.
2009-08-05 14:57:20 +00:00
</AssemblyInfo>
<ReturnValue>
<ReturnType>System.Collections.Hashtable</ReturnType>
</ReturnValue>
<Docs>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="_key">
<MemberSignature Language="C#" Value="protected int _key;" />
<MemberType>Field</MemberType>
<AssemblyInfo>
<AssemblyVersion>0.9.0.0</AssemblyVersion>
Update docs
2009-09-11 08:11:19 +00:00
<AssemblyVersion>0.9.1.0</AssemblyVersion>
Update docs
2009-10-02 13:50:16 +00:00
<AssemblyVersion>0.9.2.0</AssemblyVersion>
Update API to 0.10.25.2
2010-02-01 09:44:21 +00:00
<AssemblyVersion>0.9.3.0</AssemblyVersion>
Use internal glib-sharp copy everywhere and make it work side-by-side with real glib-sharp glib-sharp will only get a new release with the new API that we need for 3.0 in a year or something. Instead of waiting a year before we can release something we now have our own internal copy of glib-sharp trunk that will be dropped once glib-sharp 3.0 is released. Everything is now compilable and working without any additional patches.
2009-08-05 14:57:20 +00:00
</AssemblyInfo>
<ReturnValue>
<ReturnType>System.Int32</ReturnType>
</ReturnValue>
<Docs>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="_NextKey">
<MemberSignature Language="C#" Value="protected static int _NextKey;" />
<MemberType>Field</MemberType>
<AssemblyInfo>
<AssemblyVersion>0.9.0.0</AssemblyVersion>
Update docs
2009-09-11 08:11:19 +00:00
<AssemblyVersion>0.9.1.0</AssemblyVersion>
Update docs
2009-10-02 13:50:16 +00:00
<AssemblyVersion>0.9.2.0</AssemblyVersion>
Update API to 0.10.25.2
2010-02-01 09:44:21 +00:00
<AssemblyVersion>0.9.3.0</AssemblyVersion>
Use internal glib-sharp copy everywhere and make it work side-by-side with real glib-sharp glib-sharp will only get a new release with the new API that we need for 3.0 in a year or something. Instead of waiting a year before we can release something we now have our own internal copy of glib-sharp trunk that will be dropped once glib-sharp 3.0 is released. Everything is now compilable and working without any additional patches.
2009-08-05 14:57:20 +00:00
</AssemblyInfo>
<ReturnValue>
<ReturnType>System.Int32</ReturnType>
</ReturnValue>
<Docs>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="_obj">
<MemberSignature Language="C#" Value="protected Gst.GLib.Object _obj;" />
<MemberType>Field</MemberType>
<AssemblyInfo>
<AssemblyVersion>0.9.0.0</AssemblyVersion>
Update docs
2009-09-11 08:11:19 +00:00
<AssemblyVersion>0.9.1.0</AssemblyVersion>
Update docs
2009-10-02 13:50:16 +00:00
<AssemblyVersion>0.9.2.0</AssemblyVersion>
Update API to 0.10.25.2
2010-02-01 09:44:21 +00:00
<AssemblyVersion>0.9.3.0</AssemblyVersion>
Use internal glib-sharp copy everywhere and make it work side-by-side with real glib-sharp glib-sharp will only get a new release with the new API that we need for 3.0 in a year or something. Instead of waiting a year before we can release something we now have our own internal copy of glib-sharp trunk that will be dropped once glib-sharp 3.0 is released. Everything is now compilable and working without any additional patches.
2009-08-05 14:57:20 +00:00
</AssemblyInfo>
<ReturnValue>
<ReturnType>Gst.GLib.Object</ReturnType>
</ReturnValue>
<Docs>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="AddDelegate">
<MemberSignature Language="C#" Value="public void AddDelegate (Delegate d);" />
<MemberType>Method</MemberType>
<AssemblyInfo>
<AssemblyVersion>0.9.0.0</AssemblyVersion>
Update docs
2009-09-11 08:11:19 +00:00
<AssemblyVersion>0.9.1.0</AssemblyVersion>
Update docs
2009-10-02 13:50:16 +00:00
<AssemblyVersion>0.9.2.0</AssemblyVersion>
Update API to 0.10.25.2
2010-02-01 09:44:21 +00:00
<AssemblyVersion>0.9.3.0</AssemblyVersion>
Use internal glib-sharp copy everywhere and make it work side-by-side with real glib-sharp glib-sharp will only get a new release with the new API that we need for 3.0 in a year or something. Instead of waiting a year before we can release something we now have our own internal copy of glib-sharp trunk that will be dropped once glib-sharp 3.0 is released. Everything is now compilable and working without any additional patches.
2009-08-05 14:57:20 +00:00
</AssemblyInfo>
<ReturnValue>
<ReturnType>System.Void</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="d" Type="System.Delegate" />
</Parameters>
<Docs>
<param name="d">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="Connect">
<MemberSignature Language="C#" Value="protected void Connect (string name, Delegate cb, int flags);" />
<MemberType>Method</MemberType>
<AssemblyInfo>
<AssemblyVersion>0.9.0.0</AssemblyVersion>
Update docs
2009-09-11 08:11:19 +00:00
<AssemblyVersion>0.9.1.0</AssemblyVersion>
Update docs
2009-10-02 13:50:16 +00:00
<AssemblyVersion>0.9.2.0</AssemblyVersion>
Update API to 0.10.25.2
2010-02-01 09:44:21 +00:00
<AssemblyVersion>0.9.3.0</AssemblyVersion>
Use internal glib-sharp copy everywhere and make it work side-by-side with real glib-sharp glib-sharp will only get a new release with the new API that we need for 3.0 in a year or something. Instead of waiting a year before we can release something we now have our own internal copy of glib-sharp trunk that will be dropped once glib-sharp 3.0 is released. Everything is now compilable and working without any additional patches.
2009-08-05 14:57:20 +00:00
</AssemblyInfo>
<ReturnValue>
<ReturnType>System.Void</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="name" Type="System.String" />
<Parameter Name="cb" Type="System.Delegate" />
<Parameter Name="flags" Type="System.Int32" />
</Parameters>
<Docs>
<param name="name">To be added.</param>
<param name="cb">To be added.</param>
<param name="flags">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="Disconnect">
<MemberSignature Language="C#" Value="protected void Disconnect ();" />
<MemberType>Method</MemberType>
<AssemblyInfo>
<AssemblyVersion>0.9.0.0</AssemblyVersion>
Update docs
2009-09-11 08:11:19 +00:00
<AssemblyVersion>0.9.1.0</AssemblyVersion>
Update docs
2009-10-02 13:50:16 +00:00
<AssemblyVersion>0.9.2.0</AssemblyVersion>
Update API to 0.10.25.2
2010-02-01 09:44:21 +00:00
<AssemblyVersion>0.9.3.0</AssemblyVersion>
Use internal glib-sharp copy everywhere and make it work side-by-side with real glib-sharp glib-sharp will only get a new release with the new API that we need for 3.0 in a year or something. Instead of waiting a year before we can release something we now have our own internal copy of glib-sharp trunk that will be dropped once glib-sharp 3.0 is released. Everything is now compilable and working without any additional patches.
2009-08-05 14:57:20 +00:00
</AssemblyInfo>
<ReturnValue>
<ReturnType>System.Void</ReturnType>
</ReturnValue>
<Parameters />
<Docs>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="Dispose">
<MemberSignature Language="C#" Value="public void Dispose ();" />
<MemberType>Method</MemberType>
<AssemblyInfo>
<AssemblyVersion>0.9.0.0</AssemblyVersion>
Update docs
2009-09-11 08:11:19 +00:00
<AssemblyVersion>0.9.1.0</AssemblyVersion>
Update docs
2009-10-02 13:50:16 +00:00
<AssemblyVersion>0.9.2.0</AssemblyVersion>
Update API to 0.10.25.2
2010-02-01 09:44:21 +00:00
<AssemblyVersion>0.9.3.0</AssemblyVersion>
Use internal glib-sharp copy everywhere and make it work side-by-side with real glib-sharp glib-sharp will only get a new release with the new API that we need for 3.0 in a year or something. Instead of waiting a year before we can release something we now have our own internal copy of glib-sharp trunk that will be dropped once glib-sharp 3.0 is released. Everything is now compilable and working without any additional patches.
2009-08-05 14:57:20 +00:00
</AssemblyInfo>
<ReturnValue>
<ReturnType>System.Void</ReturnType>
</ReturnValue>
<Parameters />
<Docs>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="Dispose">
<MemberSignature Language="C#" Value="protected virtual void Dispose (bool disposing);" />
<MemberType>Method</MemberType>
<AssemblyInfo>
<AssemblyVersion>0.9.0.0</AssemblyVersion>
Update docs
2009-09-11 08:11:19 +00:00
<AssemblyVersion>0.9.1.0</AssemblyVersion>
Update docs
2009-10-02 13:50:16 +00:00
<AssemblyVersion>0.9.2.0</AssemblyVersion>
Update API to 0.10.25.2
2010-02-01 09:44:21 +00:00
<AssemblyVersion>0.9.3.0</AssemblyVersion>
Use internal glib-sharp copy everywhere and make it work side-by-side with real glib-sharp glib-sharp will only get a new release with the new API that we need for 3.0 in a year or something. Instead of waiting a year before we can release something we now have our own internal copy of glib-sharp trunk that will be dropped once glib-sharp 3.0 is released. Everything is now compilable and working without any additional patches.
2009-08-05 14:57:20 +00:00
</AssemblyInfo>
<ReturnValue>
<ReturnType>System.Void</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="disposing" Type="System.Boolean" />
</Parameters>
<Docs>
<param name="disposing">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="Finalize">
<MemberSignature Language="C#" Value="~SignalCallback ();" />
<MemberType>Method</MemberType>
<AssemblyInfo>
<AssemblyVersion>0.9.0.0</AssemblyVersion>
Update docs
2009-09-11 08:11:19 +00:00
<AssemblyVersion>0.9.1.0</AssemblyVersion>
Update docs
2009-10-02 13:50:16 +00:00
<AssemblyVersion>0.9.2.0</AssemblyVersion>
Update API to 0.10.25.2
2010-02-01 09:44:21 +00:00
<AssemblyVersion>0.9.3.0</AssemblyVersion>
Use internal glib-sharp copy everywhere and make it work side-by-side with real glib-sharp glib-sharp will only get a new release with the new API that we need for 3.0 in a year or something. Instead of waiting a year before we can release something we now have our own internal copy of glib-sharp trunk that will be dropped once glib-sharp 3.0 is released. Everything is now compilable and working without any additional patches.
2009-08-05 14:57:20 +00:00
</AssemblyInfo>
<ReturnValue>
<ReturnType>System.Void</ReturnType>
</ReturnValue>
<Parameters />
<Docs>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="RemoveDelegate">
<MemberSignature Language="C#" Value="public void RemoveDelegate (Delegate d);" />
<MemberType>Method</MemberType>
<AssemblyInfo>
<AssemblyVersion>0.9.0.0</AssemblyVersion>
Update docs
2009-09-11 08:11:19 +00:00
<AssemblyVersion>0.9.1.0</AssemblyVersion>
Update docs
2009-10-02 13:50:16 +00:00
<AssemblyVersion>0.9.2.0</AssemblyVersion>
Update API to 0.10.25.2
2010-02-01 09:44:21 +00:00
<AssemblyVersion>0.9.3.0</AssemblyVersion>
Use internal glib-sharp copy everywhere and make it work side-by-side with real glib-sharp glib-sharp will only get a new release with the new API that we need for 3.0 in a year or something. Instead of waiting a year before we can release something we now have our own internal copy of glib-sharp trunk that will be dropped once glib-sharp 3.0 is released. Everything is now compilable and working without any additional patches.
2009-08-05 14:57:20 +00:00
</AssemblyInfo>
<ReturnValue>
<ReturnType>System.Void</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="d" Type="System.Delegate" />
</Parameters>
<Docs>
<param name="d">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
</Members>
</Type>
Reference in a new issue Copy permalink