diff options
| author | wm4 <wm4@nowhere> | 2016-09-04 15:43:12 +0200 |
|---|---|---|
| committer | wm4 <wm4@nowhere> | 2016-09-04 18:05:36 +0200 |
| commit | 2619d8eff4e2c1cf54574acfbd0cd5895e362e45 (patch) | |
| tree | d7ae05f444c26314464b72e890874ba08394ee44 /player/playloop.c | |
| parent | d889d1fbaa28abec6b71d2ee0d9b9f8e62c09c04 (diff) | |
| download | mpv-2619d8eff4e2c1cf54574acfbd0cd5895e362e45.tar.bz2 mpv-2619d8eff4e2c1cf54574acfbd0cd5895e362e45.tar.xz | |
client API: implement mpv_suspend/resume slightly differently
Why do these API calls even still exist? I don't know, and maybe they
don't make any sense anymore. But whether they should be removed or not
is not a decision I want to make now. I want to get rid of
mp_dispatch_suspend/resume(), though. So implement the client APIs
slightly differently.
Diffstat (limited to 'player/playloop.c')
| -rw-r--r-- | player/playloop.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/player/playloop.c b/player/playloop.c index 079d3a952a..449813c777 100644 --- a/player/playloop.c +++ b/player/playloop.c @@ -70,6 +70,8 @@ void mp_process_input(struct MPContext *mpctx) mp_cmd_free(cmd); mp_dispatch_queue_process(mpctx->dispatch, 0); } + while (mpctx->suspend_count) + mp_dispatch_queue_process(mpctx->dispatch, 100); } double get_relative_time(struct MPContext *mpctx) |