summaryrefslogtreecommitdiffstats
path: root/player/client.c
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2020-03-07 12:39:03 +0100
committerwm4 <wm4@nowhere>2020-03-07 12:47:46 +0100
commita56d5bdb53cc0f0a7c2a6bb91ca3240054e43db2 (patch)
treeb3cd7bb633ec0d80e2806c54a1a1644c4c6fbf85 /player/client.c
parent7f1bd0f30bec864453df5525e8af0b340f5746b4 (diff)
downloadmpv-a56d5bdb53cc0f0a7c2a6bb91ca3240054e43db2.tar.bz2
mpv-a56d5bdb53cc0f0a7c2a6bb91ca3240054e43db2.tar.xz
client API: always reset new_property_events fields
This was not reset in the num_properties==0 case. This didn't really matter, but for debugging it's slightly nicer to see new_property_events reset once the client thread is done with it.
Diffstat (limited to 'player/client.c')
-rw-r--r--player/client.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/player/client.c b/player/client.c
index 460632805f..91c86f4a88 100644
--- a/player/client.c
+++ b/player/client.c
@@ -1735,7 +1735,8 @@ static bool gen_property_change_event(struct mpv_handle *ctx)
while (1) {
if (ctx->cur_property_index >= ctx->num_properties) {
- if (!ctx->new_property_events || !ctx->num_properties)
+ ctx->new_property_events &= ctx->num_properties > 0;
+ if (!ctx->new_property_events)
break;
ctx->new_property_events = false;
ctx->cur_property_index = 0;