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

183 lines
6 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="MainLoop" FullName="Gst.GLib.MainLoop">
<TypeSignature Language="C#" Value="public class MainLoop" />
<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.Object</BaseTypeName>
</Base>
<Interfaces />
<Docs>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
<Members>
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public MainLoop ();" />
<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 />
<Docs>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
Update docs
2009-09-03 09:09:11 +00:00
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public MainLoop (Gst.GLib.MainContext context);" />
<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-09-03 09:09:11 +00:00
</AssemblyInfo>
<Parameters>
<Parameter Name="context" Type="Gst.GLib.MainContext" />
</Parameters>
<Docs>
<param name="context">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public MainLoop (Gst.GLib.MainContext context, bool is_running);" />
<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-09-03 09:09:11 +00:00
</AssemblyInfo>
<Parameters>
<Parameter Name="context" Type="Gst.GLib.MainContext" />
<Parameter Name="is_running" Type="System.Boolean" />
</Parameters>
<Docs>
<param name="context">To be added.</param>
<param name="is_running">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="Context">
<MemberSignature Language="C#" Value="public Gst.GLib.MainContext Context { 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>
Update docs
2009-09-03 09:09:11 +00:00
</AssemblyInfo>
<ReturnValue>
<ReturnType>Gst.GLib.MainContext</ReturnType>
</ReturnValue>
<Docs>
<summary>To be added.</summary>
<value>To be added.</value>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="Equals">
<MemberSignature Language="C#" Value="public override bool Equals (object o);" />
<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-09-03 09:09:11 +00:00
</AssemblyInfo>
<ReturnValue>
<ReturnType>System.Boolean</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="o" Type="System.Object" />
</Parameters>
<Docs>
<param name="o">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="Finalize">
<MemberSignature Language="C#" Value="~MainLoop ();" />
<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>
Update docs
2009-09-03 09:09:11 +00:00
<Member MemberName="GetHashCode">
<MemberSignature Language="C#" Value="public override int GetHashCode ();" />
<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-09-03 09:09:11 +00:00
</AssemblyInfo>
<ReturnValue>
<ReturnType>System.Int32</ReturnType>
</ReturnValue>
<Parameters />
<Docs>
<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="IsRunning">
<MemberSignature Language="C#" Value="public bool IsRunning { 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.Boolean</ReturnType>
</ReturnValue>
<Docs>
<summary>To be added.</summary>
<value>To be added.</value>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="Quit">
<MemberSignature Language="C#" Value="public void Quit ();" />
<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="Run">
<MemberSignature Language="C#" Value="public void Run ();" />
<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>
</Members>
</Type>
Reference in a new issue Copy permalink