diff options
| author | wm4 <wm4@nowhere> | 2016-05-04 17:37:54 +0200 |
|---|---|---|
| committer | wm4 <wm4@nowhere> | 2016-05-04 17:37:54 +0200 |
| commit | b2646911a900cf3cb9c6e90aa28066c7be91abaf (patch) | |
| tree | 8e867f0a82e73b9f336e437ba6a4d372600bdd49 /DOCS/client-api-changes.rst | |
| parent | 833375f88d0392cac49b30ee3a4704fbab58e814 (diff) | |
| download | mpv-b2646911a900cf3cb9c6e90aa28066c7be91abaf.tar.bz2 mpv-b2646911a900cf3cb9c6e90aa28066c7be91abaf.tar.xz | |
client API: access choices as flags if appropriate
Options/properties that are choices, and which include "yes" or "no"
values (or both) can now be read and written as MPV_FORMAT_FLAG.
For write access, rejecting flags in these cases was obnoxiously
unintuitive and inconvenient.
For read access, the value of this is less convincing, and actually it's
a major API change. At this point I probably have to admit that the
finer details of the client API are very unstable.
Diffstat (limited to 'DOCS/client-api-changes.rst')
| -rw-r--r-- | DOCS/client-api-changes.rst | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/DOCS/client-api-changes.rst b/DOCS/client-api-changes.rst index 44490ea79d..8fcdf83e32 100644 --- a/DOCS/client-api-changes.rst +++ b/DOCS/client-api-changes.rst @@ -41,6 +41,11 @@ API changes is invoked with that type directly. This new behavior is equivalent to mpv_set_option(). This also affects the mp.set_property_native() Lua function. + - generally, setting choice options/properties with "yes"/"no" options + can now be set as MPV_FORMAT_FLAG + - reading a choice property as MPV_FORMAT_NODE will now return a + MPV_FORMAT_FLAG value if the choice is "yes" (true) or "no" (false) + This implicitly affects Lua and JSON IPC interfaces as well. --- mpv 0.12.0 --- 1.20 - deprecate "GL_MP_D3D_interfaces"/"glMPGetD3DInterface", and introduce "GL_MP_MPGetNativeDisplay"/"glMPGetNativeDisplay" (this is a |