From 1393d79417278dfa63a7a5c767093eaf3504edce Mon Sep 17 00:00:00 2001 From: wm4 Date: Thu, 1 Sep 2016 20:57:33 +0200 Subject: command: fix or document some property/option consistency issues Make some existing properties behave more like options. This mostly means they don't deny access if the associated component is not active, but redirects to the option. One kind of fishy change is that we apply --brightness etc. only if they're not set to the default value. This won't necessarily work with --vo=xv, but affects only cases where 1. the Xv adapter has been changed to non-defaults, and 2. the user tries to reset them with mpv by passing e.g. --brightness=0. We don't care about Xv, and the noted use-case is dumb, so this change is acceptable. --- DOCS/interface-changes.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'DOCS/interface-changes.rst') diff --git a/DOCS/interface-changes.rst b/DOCS/interface-changes.rst index 478285a394..9bfbdcf3b0 100644 --- a/DOCS/interface-changes.rst +++ b/DOCS/interface-changes.rst @@ -26,7 +26,9 @@ Interface changes but do not use the mechanism for negation options. (Also see client API change for API version 1.23.) - add almost all options to the property list, meaning you can change - options without adding "options/" to the property name + options without adding "options/" to the property name (a new section + has been added to the manpage describing some conflicting behavior + between options and properties) - rename the following properties - "demuxer" -> "current-demuxer" - "fps" -> "container-fps" -- cgit v1.2.3