diff options
| author | wm4 <wm4@nowhere> | 2014-10-07 21:01:19 +0200 |
|---|---|---|
| committer | wm4 <wm4@nowhere> | 2014-10-07 21:01:19 +0200 |
| commit | 128bb68d290107c15f2c5b38593048da6e321f40 (patch) | |
| tree | 084aca6e7a42206593e486033339f1fcd192aa04 /DOCS/man | |
| parent | 9541537e32ce220bb6b603ad505217a904d3bf50 (diff) | |
| download | mpv-128bb68d290107c15f2c5b38593048da6e321f40.tar.bz2 mpv-128bb68d290107c15f2c5b38593048da6e321f40.tar.xz | |
client API: clarify pause/unpause events, modify core-idle property
Whether you consider the semantics weird or not depends on your use
case, but I suppose it's a bit confusing anyway. At this point, we keep
MPV_EVENT_PAUSE/UNPAUSE for compatibility only.
Make the "core-idle" property somewhat more useful in this context.
Diffstat (limited to 'DOCS/man')
| -rw-r--r-- | DOCS/man/input.rst | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/DOCS/man/input.rst b/DOCS/man/input.rst index ae3454c51f..89be9dcaec 100644 --- a/DOCS/man/input.rst +++ b/DOCS/man/input.rst @@ -828,6 +828,10 @@ Property list be different ``pause`` in special situations, such as when the player pauses itself due to low network cache. + This also returns ``yes`` if playback is restarting or if nothing is + playing at all. In other words, it's only ``no`` if there's actually + video playing. (Behavior since mpv 0.7.0.) + ``cache`` Network cache fill state (0-100.0). |