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/FractionRange.xml

213 lines
7.3 KiB
XML
Raw Normal View History

Update docs
2009-04-12 18:56:06 +00:00
<Type Name="FractionRange" FullName="Gst.FractionRange">
<TypeSignature Language="C#" Value="public struct FractionRange" />
<AssemblyInfo>
<AssemblyName>gstreamer-sharp</AssemblyName>
Update docs
2009-05-28 08:36:44 +00:00
<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-04-12 18:56:06 +00:00
<AssemblyVersion>0.9.5.99</AssemblyVersion>
</AssemblyInfo>
<Base>
<BaseTypeName>System.ValueType</BaseTypeName>
</Base>
<Interfaces />
<Docs>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
<Members>
Update docs
2009-04-27 10:48:55 +00:00
<Member MemberName=".ctor">
Update docs
2009-04-12 18:56:06 +00:00
<MemberSignature Language="C#" Value="public FractionRange (GLib.Value val);" />
<MemberType>Constructor</MemberType>
<AssemblyInfo>
<AssemblyVersion>0.9.5.99</AssemblyVersion>
</AssemblyInfo>
First try to create a code generator for element bindings
2009-05-26 13:32:27 +00:00
<Parameters>
<Parameter Name="val" Type="GLib.Value" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
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
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public FractionRange (Gst.GLib.Value 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.Value" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
First try to create a code generator for element bindings
2009-05-26 13:32:27 +00:00
<Member MemberName=".ctor">
Update docs
2009-04-12 18:56:06 +00:00
<MemberSignature Language="C#" Value="public FractionRange (Gst.Fraction min, Gst.Fraction max);" />
<MemberType>Constructor</MemberType>
<AssemblyInfo>
Update docs
2009-05-28 08:36:44 +00:00
<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-04-12 18:56:06 +00:00
<AssemblyVersion>0.9.5.99</AssemblyVersion>
</AssemblyInfo>
First try to create a code generator for element bindings
2009-05-26 13:32:27 +00:00
<Parameters>
<Parameter Name="min" Type="Gst.Fraction" />
<Parameter Name="max" Type="Gst.Fraction" />
</Parameters>
<Docs>
<param name="min">To be added.</param>
<param name="max">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="GType">
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
<MemberSignature Language="C#" Value="public static Gst.GLib.GType GType { get; }" />
Update docs
2009-04-12 18:56:06 +00:00
<MemberType>Property</MemberType>
<AssemblyInfo>
Update docs
2009-05-28 08:36:44 +00:00
<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-04-12 18:56:06 +00:00
<AssemblyVersion>0.9.5.99</AssemblyVersion>
</AssemblyInfo>
First try to create a code generator for element bindings
2009-05-26 13:32:27 +00:00
<ReturnValue>
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
<ReturnType>Gst.GLib.GType</ReturnType>
First try to create a code generator for element bindings
2009-05-26 13:32:27 +00:00
</ReturnValue>
<Docs>
<summary>To be added.</summary>
<value>To be added.</value>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="Max">
Update docs
2009-04-12 18:56:06 +00:00
<MemberSignature Language="C#" Value="public Gst.Fraction Max;" />
<MemberType>Field</MemberType>
<AssemblyInfo>
Update docs
2009-05-28 08:36:44 +00:00
<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-04-12 18:56:06 +00:00
<AssemblyVersion>0.9.5.99</AssemblyVersion>
</AssemblyInfo>
First try to create a code generator for element bindings
2009-05-26 13:32:27 +00:00
<ReturnValue>
<ReturnType>Gst.Fraction</ReturnType>
</ReturnValue>
<Docs>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="Min">
Update docs
2009-04-12 18:56:06 +00:00
<MemberSignature Language="C#" Value="public Gst.Fraction Min;" />
<MemberType>Field</MemberType>
<AssemblyInfo>
Update docs
2009-05-28 08:36:44 +00:00
<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-04-12 18:56:06 +00:00
<AssemblyVersion>0.9.5.99</AssemblyVersion>
</AssemblyInfo>
First try to create a code generator for element bindings
2009-05-26 13:32:27 +00:00
<ReturnValue>
<ReturnType>Gst.Fraction</ReturnType>
</ReturnValue>
<Docs>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="op_Explicit">
Update docs
2009-04-12 18:56:06 +00:00
<MemberSignature Language="C#" Value="public static GLib.Value op_Explicit (Gst.FractionRange range);" />
<MemberType>Method</MemberType>
<AssemblyInfo>
<AssemblyVersion>0.9.5.99</AssemblyVersion>
</AssemblyInfo>
First try to create a code generator for element bindings
2009-05-26 13:32:27 +00:00
<ReturnValue>
<ReturnType>GLib.Value</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="range" Type="Gst.FractionRange" />
</Parameters>
<Docs>
<param name="range">To be added.</param>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
</Member>
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
<Member MemberName="op_Explicit">
<MemberSignature Language="C#" Value="public static Gst.GLib.Value op_Explicit (Gst.FractionRange range);" />
<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.Value</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="range" Type="Gst.FractionRange" />
</Parameters>
<Docs>
<param name="range">To be added.</param>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
</Member>
First try to create a code generator for element bindings
2009-05-26 13:32:27 +00:00
<Member MemberName="SetGValue">
Update docs
2009-04-27 10:48:55 +00:00
<MemberSignature Language="C#" Value="public void SetGValue (ref GLib.Value val);" />
<MemberType>Method</MemberType>
<AssemblyInfo>
<AssemblyVersion>0.9.5.99</AssemblyVersion>
</AssemblyInfo>
First try to create a code generator for element bindings
2009-05-26 13:32:27 +00:00
<ReturnValue>
<ReturnType>System.Void</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="val" Type="GLib.Value&amp;" RefType="ref" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
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
<Member MemberName="SetGValue">
<MemberSignature Language="C#" Value="public void SetGValue (ref 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.Void</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="val" Type="Gst.GLib.Value&amp;" RefType="ref" />
</Parameters>
<Docs>
<param name="val">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
First try to create a code generator for element bindings
2009-05-26 13:32:27 +00:00
<Member MemberName="ToString">
<MemberSignature Language="C#" Value="public override string ToString ();" />
<MemberType>Method</MemberType>
<AssemblyInfo>
Update docs
2009-05-28 08:36:44 +00:00
<AssemblyVersion>0.9.0.0</AssemblyVersion>
Update docs
2009-09-11 08:11:19 +00:00
<AssemblyVersion>0.9.1.0</AssemblyVersion>
First try to create a code generator for element bindings
2009-05-26 13:32:27 +00:00
<AssemblyVersion>0.9.5.99</AssemblyVersion>
</AssemblyInfo>
<ReturnValue>
<ReturnType>System.String</ReturnType>
</ReturnValue>
<Parameters />
<Docs>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
Update docs
2009-04-27 10:48:55 +00:00
</Member>
</Members>
Update docs
2009-04-12 18:56:06 +00:00
</Type>
Reference in a new issue Copy permalink