From a668ae0ff90c43ebcdea4f581aef0c98aeebd382 Mon Sep 17 00:00:00 2001 From: wm4 Date: Sun, 9 Sep 2012 02:08:08 +0200 Subject: 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. --- mp_osd.h | 1 + 1 file changed, 1 insertion(+) (limited to 'mp_osd.h') diff --git a/mp_osd.h b/mp_osd.h index a6797ed318..86eed3a142 100644 --- a/mp_osd.h +++ b/mp_osd.h @@ -33,6 +33,7 @@ #define MAX_OSD_LEVEL 3 #define MAX_TERM_OSD_LEVEL 1 +#define OSD_LEVEL_INVISIBLE 4 struct MPContext; -- cgit v1.2.3