diff options
author | wm4 <wm4@nowhere> | 2014-02-24 22:49:07 +0100 |
---|---|---|
committer | wm4 <wm4@nowhere> | 2014-02-24 22:50:25 +0100 |
commit | 0adb8a9aaf1e1c76300d717a0a3dd04849e70d1d (patch) | |
tree | 3dd2387c4eacd986a25a6025fac2e99aad621396 /player/command.c | |
parent | 5d7007c6448660b2bdbc7758db7f486157ff1fa2 (diff) | |
download | mpv-0adb8a9aaf1e1c76300d717a0a3dd04849e70d1d.tar.bz2 mpv-0adb8a9aaf1e1c76300d717a0a3dd04849e70d1d.tar.xz |
client API: report pause/unpause reason
Not sure about this... might redo.
At least this provides a case of a broadcasted event, which requires
per-event data allocation.
See github issue #576.
Diffstat (limited to 'player/command.c')
-rw-r--r-- | player/command.c | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/player/command.c b/player/command.c index bb63b8863a..11a5422add 100644 --- a/player/command.c +++ b/player/command.c @@ -877,9 +877,9 @@ static int mp_property_pause(m_option_t *prop, int action, void *arg, if (action == M_PROPERTY_SET) { if (*(int *)arg) { - pause_player(mpctx); + pause_player(mpctx, PAUSE_BY_COMMAND); } else { - unpause_player(mpctx); + unpause_player(mpctx, PAUSE_BY_COMMAND); } return M_PROPERTY_OK; } @@ -3369,12 +3369,12 @@ void run_command(MPContext *mpctx, mp_cmd_t *cmd) } if (cmd->flags & MP_PAUSING) - pause_player(mpctx); + pause_player(mpctx, PAUSE_BY_COMMAND); if (cmd->flags & MP_PAUSING_TOGGLE) { if (opts->pause) - unpause_player(mpctx); + unpause_player(mpctx, PAUSE_BY_COMMAND); else - pause_player(mpctx); + pause_player(mpctx, PAUSE_BY_COMMAND); } } |