diff options
| author | wm4 <wm4@nowhere> | 2015-06-20 21:40:47 +0200 |
|---|---|---|
| committer | wm4 <wm4@nowhere> | 2015-06-20 21:40:47 +0200 |
| commit | 23b83c6676c17963a59febeac72fdc73a4198769 (patch) | |
| tree | ac79ca8400a0a7e2c45819fb71362783bb114462 /DOCS/client-api-changes.rst | |
| parent | 34fce974c60177444d23ab1b658545b32046785f (diff) | |
| download | mpv-23b83c6676c17963a59febeac72fdc73a4198769.tar.bz2 mpv-23b83c6676c17963a59febeac72fdc73a4198769.tar.xz | |
client API: allow using msg-level option for log messages
Client API users can enable log output with mpv_request_log_messages().
But you can enable only a single log level. This is normally enough, but
the --msg-level option (which controls the terminal log level) provides
more flexibility. Due to internal complexity, it would be hard to
provide the same flexibility for each client API handle. But there's a
simple way to achieve basically the same thing: add an option that sends
log messages to the API handle, which would also be printed to the
terminal as by --msg-level.
The only change is that we don't disable this logic if the terminal is
disabled. Instead we check for this before the message is output, which
in theory can lower performance if messages are being spammed. It could
be handled with some more effort, but the gain would be negligible.
Diffstat (limited to 'DOCS/client-api-changes.rst')
| -rw-r--r-- | DOCS/client-api-changes.rst | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/DOCS/client-api-changes.rst b/DOCS/client-api-changes.rst index 241b7569d4..54fe585b1b 100644 --- a/DOCS/client-api-changes.rst +++ b/DOCS/client-api-changes.rst @@ -32,6 +32,7 @@ API changes :: + 1.19 - mpv_request_log_messages() now accepts "terminal-default" as parameter 1.18 - add MPV_END_FILE_REASON_REDIRECT, and change behavior of MPV_EVENT_END_FILE accordingly - a bunch of interface-changes.rst changes |