From 0adb8a9aaf1e1c76300d717a0a3dd04849e70d1d Mon Sep 17 00:00:00 2001 From: wm4 Date: Mon, 24 Feb 2014 22:49:07 +0100 Subject: 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. --- DOCS/man/en/lua.rst | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) (limited to 'DOCS/man') diff --git a/DOCS/man/en/lua.rst b/DOCS/man/en/lua.rst index b84984e6ce..338ffec6af 100644 --- a/DOCS/man/en/lua.rst +++ b/DOCS/man/en/lua.rst @@ -365,6 +365,25 @@ List of events ``pause`` Playback was paused. + Has the following event fields: + + ``real_paused`` + Current playback pause state as boolean. + + ``user_paused`` + User requested pause state. + + ``by_command`` + If the action was triggered by an input command (or via an user key + binding). It's false if it was an automatic action. + + ``by_cache`` + If the action was triggered by a low (or recovering) cache state. + + ``by_keep_open`` + If the pausing was triggered because the end of playback was reached, + and the "keep-open" option is enabled, 0 otherwise. + ``unpause`` Playback was unpaused. -- cgit v1.2.3