mirrors/gstreamer
mirrors/gstreamer
1
1
Fork 0
mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2024-12-22 16:26:39 +00:00
Code Issues 1 Projects Releases Wiki Activity
gstreamer/doc/en/Gst.GLib/Value.xml

896 lines
31 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="Value" FullName="Gst.GLib.Value">
<TypeSignature Language="C#" Value="public struct Value : 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>
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.ValueType</BaseTypeName>
</Base>
<Interfaces>
<Interface>
<InterfaceName>System.IDisposable</InterfaceName>
</Interface>
</Interfaces>
<Docs>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
<Members>
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public Value (Gst.GLib.GInterfaceAdapter val);" />
<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>
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="val" Type="Gst.GLib.GInterfaceAdapter" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public Value (Gst.GLib.GType gtype);" />
<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>
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="gtype" Type="Gst.GLib.GType" />
</Parameters>
<Docs>
<param name="gtype">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public Value (Gst.GLib.Object val);" />
<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>
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="val" Type="Gst.GLib.Object" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public Value (Gst.GLib.ValueArray val);" />
<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>
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="val" Type="Gst.GLib.ValueArray" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public Value (bool val);" />
<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>
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="val" Type="System.Boolean" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public Value (byte val);" />
<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>
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="val" Type="System.Byte" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public Value (double val);" />
<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>
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="val" Type="System.Double" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public Value (int val);" />
<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>
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="val" Type="System.Int32" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public Value (long val);" />
<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>
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="val" Type="System.Int64" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public Value (IntPtr val);" />
<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>
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="val" Type="System.IntPtr" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public Value (object obj);" />
<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>
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="System.Object" />
</Parameters>
<Docs>
<param name="obj">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public Value (sbyte val);" />
<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>
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="val" Type="System.SByte" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public Value (float val);" />
<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>
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="val" Type="System.Single" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public Value (string val);" />
<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>
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="val" Type="System.String" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public Value (string[] val);" />
<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>
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="val" Type="System.String[]" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public Value (ushort val);" />
<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>
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="val" Type="System.UInt16" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public Value (uint val);" />
<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>
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="val" Type="System.UInt32" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public Value (ulong val);" />
<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>
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="val" Type="System.UInt64" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public Value (Gst.GLib.EnumWrapper wrap, string type_name);" />
<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>
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>
<Attributes>
<Attribute>
<AttributeName>System.Obsolete("Replaced by Value(object) constructor")</AttributeName>
</Attribute>
</Attributes>
<Parameters>
<Parameter Name="wrap" Type="Gst.GLib.EnumWrapper" />
<Parameter Name="type_name" Type="System.String" />
</Parameters>
<Docs>
<param name="wrap">To be added.</param>
<param name="type_name">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public Value (Gst.GLib.Object obj, string prop_name);" />
<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>
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="prop_name" Type="System.String" />
</Parameters>
<Docs>
<param name="obj">To be added.</param>
<param name="prop_name">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public Value (Gst.GLib.Opaque val, string type_name);" />
<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>
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="val" Type="Gst.GLib.Opaque" />
<Parameter Name="type_name" Type="System.String" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<param name="type_name">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public Value (Gst.GLib.Object obj, string prop_name, Gst.GLib.EnumWrapper wrap);" />
<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>
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>
<Attributes>
<Attribute>
<AttributeName>System.Obsolete</AttributeName>
</Attribute>
</Attributes>
<Parameters>
<Parameter Name="obj" Type="Gst.GLib.Object" />
<Parameter Name="prop_name" Type="System.String" />
<Parameter Name="wrap" Type="Gst.GLib.EnumWrapper" />
</Parameters>
<Docs>
<param name="obj">To be added.</param>
<param name="prop_name">To be added.</param>
<param name="wrap">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public Value (IntPtr obj, string prop_name, Gst.GLib.Opaque val);" />
<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>
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>
<Attributes>
<Attribute>
<AttributeName>System.Obsolete</AttributeName>
</Attribute>
</Attributes>
<Parameters>
<Parameter Name="obj" Type="System.IntPtr" />
<Parameter Name="prop_name" Type="System.String" />
<Parameter Name="val" Type="Gst.GLib.Opaque" />
</Parameters>
<Docs>
<param name="obj">To be added.</param>
<param name="prop_name">To be added.</param>
<param name="val">To be added.</param>
<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>
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="Empty">
<MemberSignature Language="C#" Value="public static Gst.GLib.Value Empty;" />
<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>
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.Value</ReturnType>
</ReturnValue>
<Docs>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="Init">
<MemberSignature Language="C#" Value="public void Init (Gst.GLib.GType gtype);" />
<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>
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="gtype" Type="Gst.GLib.GType" />
</Parameters>
<Docs>
<param name="gtype">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="op_Explicit">
<MemberSignature Language="C#" Value="public static Gst.GLib.Boxed op_Explicit (Gst.GLib.Value val);" />
<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>
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.Boxed</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="val" Type="Gst.GLib.Value" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="op_Explicit">
<MemberSignature Language="C#" Value="public static Gst.GLib.EnumWrapper op_Explicit (Gst.GLib.Value val);" />
<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>
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>
<Attributes>
<Attribute>
<AttributeName>System.Obsolete("Replaced by Enum cast")</AttributeName>
</Attribute>
</Attributes>
<ReturnValue>
<ReturnType>Gst.GLib.EnumWrapper</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="val" Type="Gst.GLib.Value" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="op_Explicit">
<MemberSignature Language="C#" Value="public static Gst.GLib.Object op_Explicit (Gst.GLib.Value val);" />
<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>
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>
<Parameters>
<Parameter Name="val" Type="Gst.GLib.Value" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="op_Explicit">
<MemberSignature Language="C#" Value="public static Gst.GLib.Opaque op_Explicit (Gst.GLib.Value val);" />
<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>
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.Opaque</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="val" Type="Gst.GLib.Value" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="op_Explicit">
<MemberSignature Language="C#" Value="public static Gst.GLib.UnwrappedObject op_Explicit (Gst.GLib.Value val);" />
<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>
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>
<Attributes>
<Attribute>
Update docs
2009-09-16 06:41:09 +00:00
<AttributeName>System.Obsolete("Replaced by Gst.GLib.Object cast")</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>
<ReturnValue>
<ReturnType>Gst.GLib.UnwrappedObject</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="val" Type="Gst.GLib.Value" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="op_Explicit">
<MemberSignature Language="C#" Value="public static Gst.GLib.ValueArray op_Explicit (Gst.GLib.Value val);" />
<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>
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.ValueArray</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="val" Type="Gst.GLib.Value" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="op_Explicit">
<MemberSignature Language="C#" Value="public static bool op_Explicit (Gst.GLib.Value val);" />
<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>
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.Boolean</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="val" Type="Gst.GLib.Value" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="op_Explicit">
<MemberSignature Language="C#" Value="public static byte op_Explicit (Gst.GLib.Value val);" />
<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>
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.Byte</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="val" Type="Gst.GLib.Value" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="op_Explicit">
<MemberSignature Language="C#" Value="public static double op_Explicit (Gst.GLib.Value val);" />
<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>
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.Double</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="val" Type="Gst.GLib.Value" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="op_Explicit">
<MemberSignature Language="C#" Value="public static Enum op_Explicit (Gst.GLib.Value val);" />
<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>
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.Enum</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="val" Type="Gst.GLib.Value" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="op_Explicit">
<MemberSignature Language="C#" Value="public static int op_Explicit (Gst.GLib.Value val);" />
<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>
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>
<Parameters>
<Parameter Name="val" Type="Gst.GLib.Value" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="op_Explicit">
<MemberSignature Language="C#" Value="public static long op_Explicit (Gst.GLib.Value val);" />
<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>
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.Int64</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="val" Type="Gst.GLib.Value" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="op_Explicit">
<MemberSignature Language="C#" Value="public static IntPtr op_Explicit (Gst.GLib.Value val);" />
<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>
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.IntPtr</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="val" Type="Gst.GLib.Value" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="op_Explicit">
<MemberSignature Language="C#" Value="public static sbyte op_Explicit (Gst.GLib.Value val);" />
<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>
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.SByte</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="val" Type="Gst.GLib.Value" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="op_Explicit">
<MemberSignature Language="C#" Value="public static float op_Explicit (Gst.GLib.Value val);" />
<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>
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.Single</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="val" Type="Gst.GLib.Value" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="op_Explicit">
<MemberSignature Language="C#" Value="public static string op_Explicit (Gst.GLib.Value val);" />
<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>
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.String</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="val" Type="Gst.GLib.Value" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="op_Explicit">
<MemberSignature Language="C#" Value="public static string[] op_Explicit (Gst.GLib.Value val);" />
<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>
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.String[]</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="val" Type="Gst.GLib.Value" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="op_Explicit">
<MemberSignature Language="C#" Value="public static ushort op_Explicit (Gst.GLib.Value val);" />
<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>
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.UInt16</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="val" Type="Gst.GLib.Value" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="op_Explicit">
<MemberSignature Language="C#" Value="public static uint op_Explicit (Gst.GLib.Value val);" />
<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>
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>
<Parameters>
<Parameter Name="val" Type="Gst.GLib.Value" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="op_Explicit">
<MemberSignature Language="C#" Value="public static ulong op_Explicit (Gst.GLib.Value val);" />
<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>
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.UInt64</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="val" Type="Gst.GLib.Value" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="Val">
<MemberSignature Language="C#" Value="public object Val { set; get; }" />
<MemberType>Property</MemberType>
<AssemblyInfo>
<AssemblyVersion>0.9.0.0</AssemblyVersion>
Update docs
2009-09-11 08:11:19 +00:00
<AssemblyVersion>0.9.1.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.Object</ReturnType>
</ReturnValue>
<Docs>
<summary>To be added.</summary>
<value>To be added.</value>
<remarks>To be added.</remarks>
</Docs>
</Member>
</Members>
</Type>
Reference in a new issue Copy permalink