This extension defines a feature, log, which allows plugins to print log
messages with an API similar to the standard C printf function. This allows,
for example, plugin logs to be nicely presented to the user in a graphical user
interface.
Different log levels are defined by URI and passed as an LV2_URID. This extensions defines standard levels which are expected to be understood by all implementations and should be sufficient in most cases, but advanced implementations may define and use additional levels to suit their needs.
Index
Classes
Error
Class| Label | Error |
|---|---|
| Subclass of | Entry |
An error message.
An error should only be posted when a serious unexpected error occurs, and should be actively shown to the user by the host.
Note
Class| Label | Note |
|---|---|
| Subclass of | Entry |
An informative message.
A note records some useful piece of information, but may be ignored. The host should provide passive access to note entries to the user.
Trace
Class| Label | Trace |
|---|---|
| Subclass of | Entry |
A debugging trace message.
A trace should not be displayed during normal operation, but the host may implement an option to display them for debugging purposes.
This entry type is special in that one may be posted in a real-time thread. It is assumed that if debug tracing is enabled, real-time performance is not a concern. However, the host MUST guarantee that posting a trace is real-time safe if debug tracing is not enabled (for example, by simply ignoring the call as early as possible).
Instances
log
Instance| Label | log |
|---|---|
| Type | lv2:Feature |
Logging feature.
A feature which plugins may use to log messages. To support this feature, the host must pass an LV2_Feature to LV2_Descriptor::instantiate() with URI LV2_LOG__log and data pointed to an instance of LV2_Log_Log.
A log entry.
Subclasses of this are passed as the
typeparameter to LV2_Log_Log methods to describe the nature of the log entry.