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

305 lines
12 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="Log" FullName="Gst.GLib.Log">
<TypeSignature Language="C#" Value="public class Log" />
<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 />
<Docs>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
<Members>
<Member MemberName=".ctor">
<MemberSignature Language="C#" Value="public Log ();" />
<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 />
<Docs>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="DefaultHandler">
<MemberSignature Language="C#" Value="public static void DefaultHandler (string logDomain, Gst.GLib.LogLevelFlags logLevel, string message);" />
<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="logDomain" Type="System.String" />
<Parameter Name="logLevel" Type="Gst.GLib.LogLevelFlags" />
<Parameter Name="message" Type="System.String" />
</Parameters>
<Docs>
<param name="logDomain">To be added.</param>
<param name="logLevel">To be added.</param>
<param name="message">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="PrintLogFunction">
<MemberSignature Language="C#" Value="public static void PrintLogFunction (string domain, Gst.GLib.LogLevelFlags level, string message);" />
<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="domain" Type="System.String" />
<Parameter Name="level" Type="Gst.GLib.LogLevelFlags" />
<Parameter Name="message" Type="System.String" />
</Parameters>
<Docs>
<param name="domain">To be added.</param>
<param name="level">To be added.</param>
<param name="message">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="PrintTraceLogFunction">
<MemberSignature Language="C#" Value="public static void PrintTraceLogFunction (string domain, Gst.GLib.LogLevelFlags level, string message);" />
<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="domain" Type="System.String" />
<Parameter Name="level" Type="Gst.GLib.LogLevelFlags" />
<Parameter Name="message" Type="System.String" />
</Parameters>
<Docs>
<param name="domain">To be added.</param>
<param name="level">To be added.</param>
<param name="message">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="RemoveLogHandler">
<MemberSignature Language="C#" Value="public static void RemoveLogHandler (string logDomain, uint handlerID);" />
<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="logDomain" Type="System.String" />
<Parameter Name="handlerID" Type="System.UInt32" />
</Parameters>
<Docs>
<param name="logDomain">To be added.</param>
<param name="handlerID">To be added.</param>
<summary>To be added.</summary>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="SetAlwaysFatal">
<MemberSignature Language="C#" Value="public static Gst.GLib.LogLevelFlags SetAlwaysFatal (Gst.GLib.LogLevelFlags fatalMask);" />
<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>Gst.GLib.LogLevelFlags</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="fatalMask" Type="Gst.GLib.LogLevelFlags" />
</Parameters>
<Docs>
<param name="fatalMask">To be added.</param>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="SetAlwaysFatal">
<MemberSignature Language="C#" Value="public static Gst.GLib.LogLevelFlags SetAlwaysFatal (string logDomain, Gst.GLib.LogLevelFlags fatalMask);" />
<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>Gst.GLib.LogLevelFlags</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="logDomain" Type="System.String" />
<Parameter Name="fatalMask" Type="Gst.GLib.LogLevelFlags" />
</Parameters>
<Docs>
<param name="logDomain">To be added.</param>
<param name="fatalMask">To be added.</param>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
</Member>
Update docs
2009-09-03 09:09:11 +00:00
<Member MemberName="SetDefaultHandler">
<MemberSignature Language="C#" Value="public static Gst.GLib.LogFunc SetDefaultHandler (Gst.GLib.LogFunc log_func);" />
<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>
Update docs
2009-09-03 09:09:11 +00:00
</AssemblyInfo>
<ReturnValue>
<ReturnType>Gst.GLib.LogFunc</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="log_func" Type="Gst.GLib.LogFunc" />
</Parameters>
<Docs>
<param name="log_func">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="SetLogHandler">
<MemberSignature Language="C#" Value="public static uint SetLogHandler (string logDomain, Gst.GLib.LogLevelFlags flags, Gst.GLib.LogFunc logFunc);" />
<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.UInt32</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="logDomain" Type="System.String" />
<Parameter Name="flags" Type="Gst.GLib.LogLevelFlags" />
<Parameter Name="logFunc" Type="Gst.GLib.LogFunc" />
</Parameters>
<Docs>
<param name="logDomain">To be added.</param>
<param name="flags">To be added.</param>
<param name="logFunc">To be added.</param>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="SetPrintErrorHandler">
<MemberSignature Language="C#" Value="public static Gst.GLib.PrintFunc SetPrintErrorHandler (Gst.GLib.PrintFunc handler);" />
<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>Gst.GLib.PrintFunc</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="handler" Type="Gst.GLib.PrintFunc" />
</Parameters>
<Docs>
<param name="handler">To be added.</param>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="SetPrintHandler">
<MemberSignature Language="C#" Value="public static Gst.GLib.PrintFunc SetPrintHandler (Gst.GLib.PrintFunc handler);" />
<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>Gst.GLib.PrintFunc</ReturnType>
</ReturnValue>
<Parameters>
<Parameter Name="handler" Type="Gst.GLib.PrintFunc" />
</Parameters>
<Docs>
<param name="handler">To be added.</param>
<summary>To be added.</summary>
<returns>To be added.</returns>
<remarks>To be added.</remarks>
</Docs>
</Member>
<Member MemberName="WriteLog">
<MemberSignature Language="C#" Value="public void WriteLog (string logDomain, Gst.GLib.LogLevelFlags flags, string format, object[] args);" />
<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="logDomain" Type="System.String" />
<Parameter Name="flags" Type="Gst.GLib.LogLevelFlags" />
<Parameter Name="format" Type="System.String" />
<Parameter Name="args" Type="System.Object[]">
<Attributes>
<Attribute>
<AttributeName>System.ParamArray</AttributeName>
</Attribute>
</Attributes>
</Parameter>
</Parameters>
<Docs>
<param name="logDomain">To be added.</param>
<param name="flags">To be added.</param>
<param name="format">To be added.</param>
<param name="args">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