summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2020-03-14 01:40:54 +0100
committerwm4 <wm4@nowhere>2020-03-14 01:40:54 +0100
commit7c4a550c0ed9690e441d2bd0b212d42fffbec70c (patch)
tree90a1a956a56cd553ab53edcec24b08d57a70e5aa
parent314a4a572bd3a11844314b996268f90b6e722b57 (diff)
downloadmpv-7c4a550c0ed9690e441d2bd0b212d42fffbec70c.tar.bz2
mpv-7c4a550c0ed9690e441d2bd0b212d42fffbec70c.tar.xz
DOCS/interface-changes.rst: add note about property notification changes
Commits ba70b150fbe8 and 8a4f812b76be should have mentioned this. These things should be quite useful for client API users, and thus should be mentioned in a prominent place. Although I'm not sure if anyone will understand from this gibberish what this really means.
-rw-r--r--DOCS/interface-changes.rst7
1 files changed, 7 insertions, 0 deletions
diff --git a/DOCS/interface-changes.rst b/DOCS/interface-changes.rst
index 0c9c7f6831..4463930767 100644
--- a/DOCS/interface-changes.rst
+++ b/DOCS/interface-changes.rst
@@ -38,6 +38,13 @@ Interface changes
- remove deprecated legacy hook API ("hook-add", "hook-ack"). Use either the
libmpv API (mpv_hook_add(), mpv_hook_continue()), or the Lua scripting
wrappers (mp.add_hook()).
+ - improve how property change notifications are delivered on events and on
+ hooks. In particular, a hook event is only returned to a client after all
+ changes initiated before the hook point were delivered to the same client.
+ In addition, it should no longer happen that events and property change
+ notifications were interleaved in bad ways (it could happen that a
+ property notification delivered after an event contained a value that was
+ valid only before the event happened).
--- mpv 0.32.0 ---
- change behavior when using legacy option syntax with options that start
with two dashes (``--`` instead of a ``-``). Now, using the recommended