From 9d32d62b6154784a4e38dcb0ff50b8331e9169bf Mon Sep 17 00:00:00 2001 From: wm4 Date: Thu, 9 Apr 2020 11:08:03 +0200 Subject: options: fix ab-loop-* properties These used ".min = MP_NOPTS_VALUE" to indicate certain exceptions. This broke with the recent change to how min/max are handled, which made setting min or max mean that a value range is used, thus setting max=0. Fix this by not using magic a value in .min; replace it with a proper flag. Fixes: #7596 --- options/options.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'options/options.c') diff --git a/options/options.c b/options/options.c index c7d75b0648..3536e439a0 100644 --- a/options/options.c +++ b/options/options.c @@ -447,8 +447,8 @@ static const m_option_t mp_opts[] = { {"rebase-start-time", OPT_FLAG(rebase_start_time)}, - {"ab-loop-a", OPT_TIME(ab_loop[0]), .min = MP_NOPTS_VALUE}, - {"ab-loop-b", OPT_TIME(ab_loop[1]), .min = MP_NOPTS_VALUE}, + {"ab-loop-a", OPT_TIME(ab_loop[0]), .flags = M_OPT_ALLOW_NO}, + {"ab-loop-b", OPT_TIME(ab_loop[1]), .flags = M_OPT_ALLOW_NO}, {"ab-loop-count", OPT_CHOICE(ab_loop_count, {"inf", -1}), M_RANGE(0, INT_MAX)}, -- cgit v1.2.3