summaryrefslogtreecommitdiffstats
path: root/DOCS
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2020-03-21 14:01:38 +0100
committerwm4 <wm4@nowhere>2020-03-21 19:32:50 +0100
commit26ac6ead911bedf01b20d52e0696f70459ff0be2 (patch)
treebf5d797785610e8cfbc468a38807dd387a2c3ff5 /DOCS
parent2a85e8a1864ebe1d7749dfd2748931d1f320e337 (diff)
downloadmpv-26ac6ead911bedf01b20d52e0696f70459ff0be2.tar.bz2
mpv-26ac6ead911bedf01b20d52e0696f70459ff0be2.tar.xz
player: fix subtle idle mode differences on early program start
If the user manages to run a "loadfile x append" command before the loop in mp_play_files() is entered, then the player could start playing these. This isn't expected, because appending files to the playlist in idle mode does not normally start playback. It could happen because there is a short time window where commands are processed before the loop is entered (such as running the command when a script is loaded). The idle mode semantics are pretty weird: if files were provided in advance (on the command line), then these should be played immediately. But if idle mode was already entered, and something is appended to the playlist using "append", i.e. without explicitly triggering playback, then it should remain in idle mode. Try to follow this by redefining PT_STOP to strictly mean idle mode. Remove the playlist->current check from idle_loop(), since only the stop_play field counts now (cf. what mp_set_playlist_entry() does). This actually introduces the possibility that playlist->current, and with it playlist-pos, are set to something, even though playback is not active or being started. Previously, this was only possible during state transitions, such as when changing playlist entries. Very annoyingly, this means the current way MPV_EVENT_IDLE was sent doesn't work anymore. Logically, idle mode can be "active" even if idle_loop() was not entered yet (between the time after mp_initialize() and before the loop in mp_play_files()). Instead of worrying about this, redo the "idle-active" property, and deprecate the event. See: #7543
Diffstat (limited to 'DOCS')
-rw-r--r--DOCS/client-api-changes.rst1
1 files changed, 1 insertions, 0 deletions
diff --git a/DOCS/client-api-changes.rst b/DOCS/client-api-changes.rst
index 2c0c393125..b1a61fe865 100644
--- a/DOCS/client-api-changes.rst
+++ b/DOCS/client-api-changes.rst
@@ -33,6 +33,7 @@ API changes
::
--- mpv 0.33.0 ---
+ 1.108 - Deprecate MPV_EVENT_IDLE
1.107 - Remove the deprecated qthelper.hpp. This was obviously not part of the
libmpv API, only an "additionally" provided helper, thus this is not
considered an API change. If you are maintaining a project that relies