From 89d400dc21881e63fda20e23b11a88bca6ee49d6 Mon Sep 17 00:00:00 2001 From: wm4 Date: Tue, 8 Apr 2014 22:06:39 +0200 Subject: client API: avoid redundant property change events if possible This is done simply by comparing the previous and current values. Do this only if the requested format is not MPV_FORMAT_NONE. --- libmpv/client.h | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'libmpv/client.h') diff --git a/libmpv/client.h b/libmpv/client.h index 35c193f64a..0811935476 100644 --- a/libmpv/client.h +++ b/libmpv/client.h @@ -752,6 +752,10 @@ int mpv_get_property_async(mpv_handle *ctx, uint64_t reply_userdata, * Observing a property that doesn't exist is allowed, although it may still * cause some sporadic change events. * + * If you set the format parameter to a value other than MPV_FORMAT_NONE, the + * API will suppress redundant change events by comparing the raw value against + * the previous value. + * * @param reply_userdata This will be used for the mpv_event.reply_userdata * field for the received MPV_EVENT_PROPERTY_CHANGE * events. (Also see section about asynchronous calls, -- cgit v1.2.3