Package ch.bailu.gtk.gst
Schnittstelle DebugLevel
public interface DebugLevel
-
Feldübersicht
FelderModifizierer und TypFeldBeschreibungstatic final int
The number of defined debugging levels.static final int
Debugging messages should be used when something common
happens that is not the expected default behavior, or something that's
useful to know but doesn't happen all the time (ie. per loop iteration or
buffer processed or event handled).static final int
Error messages are to be used only when an error occurred
that stops the application from keeping working correctly.static final int
Fixme messages are messages that indicate that something
in the executed code path is not fully implemented or handled yet.static final int
Informational messages should be used to keep the developer
updated about what is happening.static final int
Log messages are messages that are very common but might be
useful to know.static final int
memory dump messages are used to log (small) chunks of
data as memory dumps in the log.static final int
No debugging level specified or desired.static final int
Tracing-related messages.static final int
Warning messages are to inform about abnormal behaviour
that could lead to problems or weird behaviour later on.
-
Felddetails
-
NONE
static final int NONENo debugging level specified or desired. Used to deactivate
debugging output.- Siehe auch:
-
ERROR
static final int ERRORError messages are to be used only when an error occurred
that stops the application from keeping working correctly.
An examples is gst_element_error, which outputs a message with this priority.
It does not mean that the application is terminating as with g_error.- Siehe auch:
-
WARNING
static final int WARNINGWarning messages are to inform about abnormal behaviour
that could lead to problems or weird behaviour later on. An example of this
would be clocking issues ("your computer is pretty slow") or broken input
data ("Can't synchronize to stream.")- Siehe auch:
-
FIXME
static final int FIXMEFixme messages are messages that indicate that something
in the executed code path is not fully implemented or handled yet. Note
that this does not replace proper error handling in any way, the purpose
of this message is to make it easier to spot incomplete/unfinished pieces
of code when reading the debug log.- Siehe auch:
-
INFO
static final int INFOInformational messages should be used to keep the developer
updated about what is happening.
Examples where this should be used are when a typefind function has
successfully determined the type of the stream or when an mp3 plugin detects
the format to be used. ("This file has mono sound.")- Siehe auch:
-
DEBUG
static final int DEBUGDebugging messages should be used when something common
happens that is not the expected default behavior, or something that's
useful to know but doesn't happen all the time (ie. per loop iteration or
buffer processed or event handled).
An example would be notifications about state changes or receiving/sending
of events.- Siehe auch:
-
LOG
static final int LOGLog messages are messages that are very common but might be
useful to know. As a rule of thumb a pipeline that is running as expected
should never output anything else but LOG messages whilst processing data.
Use this log level to log recurring information in chain functions and
loop functions, for example.- Siehe auch:
-
TRACE
static final int TRACETracing-related messages.
Examples for this are referencing/dereferencing of objects.- Siehe auch:
-
MEMDUMP
static final int MEMDUMPmemory dump messages are used to log (small) chunks of
data as memory dumps in the log. They will be displayed as hexdump with
ASCII characters.- Siehe auch:
-
COUNT
static final int COUNTThe number of defined debugging levels.- Siehe auch:
-