mirror of
https://github.com/mpv-player/mpv
synced 2025-02-21 07:16:56 +00:00
7dd69ef77c
Instead of using an internal counter to keep track of the value that was set last, attempt to find the current value of the property/option in the value list, and then set the next value in the list. There are some potential problems. If a property refuses to accept a specific value, the cycle-values command will fail, and start from the same position again. It can't know that it's supposed to skip the next value. The same can happen to properties which behave "strangely", such as the "aspect" property, which will return the current aspect if you write "-1" to it. As a consequence, cycle-values can appear to get "stuck". I still think the new behavior is what users expect more, and which is generally more useful. We won't restore the ability to get the old behavior, unless we decide to revert this commit entirely. Fixes #5772, and hopefully other complaints. |
||
|---|---|---|
| .. | ||
| af.rst | ||
| ao.rst | ||
| changes.rst | ||
| encode.rst | ||
| input.rst | ||
| ipc.rst | ||
| javascript.rst | ||
| libmpv.rst | ||
| lua.rst | ||
| mpv.rst | ||
| options.rst | ||
| osc.rst | ||
| stats.rst | ||
| vf.rst | ||
| vo.rst | ||