summaryrefslogtreecommitdiffstats
path: root/player/core.h
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2016-09-04 15:43:12 +0200
committerwm4 <wm4@nowhere>2016-09-04 18:05:36 +0200
commit2619d8eff4e2c1cf54574acfbd0cd5895e362e45 (patch)
treed7ae05f444c26314464b72e890874ba08394ee44 /player/core.h
parentd889d1fbaa28abec6b71d2ee0d9b9f8e62c09c04 (diff)
downloadmpv-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/core.h')
-rw-r--r--player/core.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/player/core.h b/player/core.h
index 25eb8b71a8..bdf19a815a 100644
--- a/player/core.h
+++ b/player/core.h
@@ -224,6 +224,7 @@ enum playback_status {
typedef struct MPContext {
bool initialized;
bool autodetach;
+ int suspend_count;
struct mpv_global *global;
struct MPOpts *opts;
struct mp_log *log;