From a1000962e3ef3e4cf3f6ade8702ce055b38872a9 Mon Sep 17 00:00:00 2001 From: wm4 Date: Sat, 7 Jun 2014 10:44:21 +0200 Subject: client API: change mpv_wait_event() timeout semantics Now a negative timeout mean an infinite timeout. This is similar to the poll() system call. Apparently this is more intuitive and less confusing than specifying a "very high" value as timeout if you want to wait forever. For callers that never pass negative timeouts, nothing changes. --- libmpv/client.h | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'libmpv/client.h') diff --git a/libmpv/client.h b/libmpv/client.h index 7e2dc1b98a..58512f9586 100644 --- a/libmpv/client.h +++ b/libmpv/client.h @@ -1122,7 +1122,8 @@ int mpv_request_log_messages(mpv_handle *ctx, const char *min_level); * * @param timeout Timeout in seconds, after which the function returns even if * no event was received. A MPV_EVENT_NONE is returned on - * timeout. Values <= 0 will disable waiting. + * timeout. A value of 0 will disable waiting. Negative values + * will wait with an infinite timeout. * @return A struct containing the event ID and other data. The pointer (and * fields in the struct) stay valid until the next mpv_wait_event() * call, or until mpv_destroy() is called. You must not write to -- cgit v1.2.3