summaryrefslogtreecommitdiffstats
path: root/DOCS/client-api-changes.rst
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2017-12-17 14:03:33 +0100
committerKevin Mitchell <kevmitch@gmail.com>2017-12-17 15:45:24 -0800
commitd690ee095942c06ee3157480e970ff70b399e04e (patch)
treeee6b400daba3ca50d83a50b052ef1639c252fca1 /DOCS/client-api-changes.rst
parent9ed8ca2529524665129b6892e21740c2217286c2 (diff)
downloadmpv-d690ee095942c06ee3157480e970ff70b399e04e.tar.bz2
mpv-d690ee095942c06ee3157480e970ff70b399e04e.tar.xz
client API: change --stop-playback-on-init-failure default
This was off for mpv CLI, but on for libmpv. The motivation behind this was that it would be confusing for applications if libmpv continued playback in a severely "degraded" way (without either audio or video), and that it would be better to fail early. In reality the behavior was just a confusing difference to mpv CLI, and has confused actual users as well. Get rid of it. Not bothering with a version bump, since this is so minor, and it's easy to ensure compatibility in affected applications by just setting the option explicitly. (Also adding the missing next-release-marker in client-api-changes.rst.)
Diffstat (limited to 'DOCS/client-api-changes.rst')
-rw-r--r--DOCS/client-api-changes.rst3
1 files changed, 3 insertions, 0 deletions
diff --git a/DOCS/client-api-changes.rst b/DOCS/client-api-changes.rst
index 96c2882661..1ff828339a 100644
--- a/DOCS/client-api-changes.rst
+++ b/DOCS/client-api-changes.rst
@@ -32,9 +32,12 @@ API changes
::
+ --- mpv 0.28.0 ---
1.26 - remove glMPGetNativeDisplay("drm") support
- add mpv_opengl_cb_window_pos and mpv_opengl_cb_drm_params and
support via glMPGetNativeDisplay() for using it
+ - make --stop-playback-on-init-failure=no the default in libmpv (just
+ like in mpv CLI)
--- mpv 0.27.0 ---
1.25 - remove setting "no-" options via mpv_set_option*(). (See corresponding
deprecation in 0.23.0.)