diff options
author | wm4 <wm4@nowhere> | 2017-04-01 20:36:39 +0200 |
---|---|---|
committer | wm4 <wm4@nowhere> | 2017-04-01 20:36:39 +0200 |
commit | a071d5fcfeee4cc0ac58a4e0cf1968c8c92ff080 (patch) | |
tree | 9ad851a36cba05801f691e7360ea5001b540ef65 /input/cmd_parse.c | |
parent | ec3dd7164ceea9ceda71e05e774501874fd20924 (diff) | |
download | mpv-a071d5fcfeee4cc0ac58a4e0cf1968c8c92ff080.tar.bz2 mpv-a071d5fcfeee4cc0ac58a4e0cf1968c8c92ff080.tar.xz |
input: add "async" flag
Obviously, this has no effect on commands which do not support this
explicitly. A later commit will enable this for screenshots.
Also add some wording on mpv_command_async(), which has nothing to do
with this. Having a more elegant, unified behavior would be nice. But
the API function was not created for this - it's merely for running
commands _synchronously_ on the core, but without blocking the client
API caller (if the API user consistently uses only async functions).
Diffstat (limited to 'input/cmd_parse.c')
-rw-r--r-- | input/cmd_parse.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/input/cmd_parse.c b/input/cmd_parse.c index 01e4bb6411..b0c6c50753 100644 --- a/input/cmd_parse.c +++ b/input/cmd_parse.c @@ -49,6 +49,7 @@ static const struct flag cmd_flags[] = { {"expand-properties", 0, MP_EXPAND_PROPERTIES}, {"raw", MP_EXPAND_PROPERTIES, 0}, {"repeatable", 0, MP_ALLOW_REPEAT}, + {"async", 0, MP_ASYNC_CMD}, {0} }; |