log
type: Project
name: LV2 Log
shortdesc: A feature for writing log messages.
created: 2012-01-12
developer: me
release:
  revision: 2.4
  created: 2016-07-30
  file-release: lv2-1.14.0.tar.bz2
  blame: me
  changeset:
    item: Add lv2_log_logger_set_map() for changing the URI map of an existing logger.
release:
  revision: 2.2
  created: 2014-01-04
  file-release: lv2-1.8.0.tar.bz2
  blame: me
  changeset:
    item: Add missing include string.h to logger.h for memset.
release:
  revision: 2.0
  created: 2013-01-08
  file-release: lv2-1.4.0.tar.bz2
  blame: me
  changeset:
    item: Add logger convenience API.
release:
  revision: 1.0
  created: 2012-04-17
  file-release: lv2-1.0.0.tar.bz2
  blame: me
  changeset:
    item: Initial release.
documentation: This extension defines a feature, log: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.

Log Entry
type: Class
documentation: Subclasses of this are passed as the `type` parameter to LV2_Log_Log methods to describe the nature of the log entry.

Error
documentation: An error should only be posted when a serious unexpected error occurs, and should be actively shown to the user by the host.

Note
documentation: A note records some useful piece of information, but may be ignored. The host should provide passive access to note entries to the user.

Warning
documentation: A warning should be posted when an unexpected, but non-critical, error occurs. The host should provide passive access to warnings entries to the user, but may also choose to actively show them.

Trace
documentation: 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).

log
documentation: 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.