summaryrefslogtreecommitdiffstats
path: root/DOCS
diff options
context:
space:
mode:
Diffstat (limited to 'DOCS')
-rw-r--r--DOCS/interface-changes/floating-point_property_expansion.txt1
-rw-r--r--DOCS/man/input.rst8
2 files changed, 8 insertions, 1 deletions
diff --git a/DOCS/interface-changes/floating-point_property_expansion.txt b/DOCS/interface-changes/floating-point_property_expansion.txt
new file mode 100644
index 0000000000..eeda63d113
--- /dev/null
+++ b/DOCS/interface-changes/floating-point_property_expansion.txt
@@ -0,0 +1 @@
+add `>` for fixed precision floating-point property expansion
diff --git a/DOCS/man/input.rst b/DOCS/man/input.rst
index bb353cd117..341d20c926 100644
--- a/DOCS/man/input.rst
+++ b/DOCS/man/input.rst
@@ -3766,7 +3766,9 @@ Normally, properties are formatted as human-readable text, meant to be
displayed on OSD or on the terminal. It is possible to retrieve an unformatted
(raw) value from a property by prefixing its name with ``=``. These raw values
can be parsed by other programs and follow the same conventions as the options
-associated with the properties.
+associated with the properties. Additionally, there is a ``>`` prefix to format
+human-readable text, with fixed precision for floating-point values. This is
+useful for printing values where a constant width is important.
.. admonition:: Examples
@@ -3775,6 +3777,10 @@ associated with the properties.
- ``${=time-pos}`` expands to ``863.4`` (same time, plus 400 milliseconds -
milliseconds are normally not shown in the formatted case)
+ - ``${avsync}`` expands to ``+0.003``
+ - ``${>avsync}`` expands to ``+0.0030``
+ - ``${=avsync}`` expands to ``0.003028``
+
Sometimes, the difference in amount of information carried by raw and formatted
property values can be rather big. In some cases, raw values have more
information, like higher precision than seconds with ``time-pos``. Sometimes