From 128bb68d290107c15f2c5b38593048da6e321f40 Mon Sep 17 00:00:00 2001 From: wm4 Date: Tue, 7 Oct 2014 21:01:19 +0200 Subject: 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. --- player/command.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'player') diff --git a/player/command.c b/player/command.c index 8d4e3170a9..4b1f37288c 100644 --- a/player/command.c +++ b/player/command.c @@ -1020,7 +1020,8 @@ static int mp_property_core_idle(void *ctx, struct m_property *prop, int action, void *arg) { MPContext *mpctx = ctx; - return m_property_flag_ro(action, arg, mpctx->paused); + bool idle = mpctx->paused || !mpctx->restart_complete || !mpctx->playing; + return m_property_flag_ro(action, arg, idle); } static int mp_property_eof_reached(void *ctx, struct m_property *prop, -- cgit v1.2.3