diff options
author | wm4 <wm4@nowhere> | 2012-09-09 02:08:08 +0200 |
---|---|---|
committer | wm4 <wm4@nowhere> | 2012-10-12 10:10:30 +0200 |
commit | a668ae0ff90c43ebcdea4f581aef0c98aeebd382 (patch) | |
tree | e1de875829472b0d6230372f02d7a81c9bcbeef0 /stream | |
parent | 6096966dee420179b65f4d2d3b93207419e58471 (diff) | |
download | mpv-a668ae0ff90c43ebcdea4f581aef0c98aeebd382.tar.bz2 mpv-a668ae0ff90c43ebcdea4f581aef0c98aeebd382.tar.xz |
commands: change input commands to make OSD usage explicit
Most input commands had their own policy whether to display an OSD
message for user feedback or not. Some commands had two variants, one
that showed an OSD message and one that didn't (e.g. step_property_osd
and step_property).
Change it such that all commands show a message on the OSD. Add a
"no-osd" modifier that disables OSD for that command. Rename the
"step_property" and "step_property_osd" command to "switch", and rename
"set_property" and "set_property_osd" to "set".
Note that commands which haven't used OSD before still don't use OSD.
That will possibly be fixed later. (E.g. "screenshot" could display an
OSD message instead of just printing a message on the terminal.)
The chapter and edition properties still produce OSD messages even with
"no-osd", because they don't map so well to the property_osd_display[]
mechanism.
Diffstat (limited to 'stream')
0 files changed, 0 insertions, 0 deletions