mpv/input
Niklas Haas ba1943ac00 msg: reinterpret a bunch of message levels
I've decided that MP_TRACE means “noisy spam per frame”, whereas
MP_DBG just means “more verbose debugging messages than MSGL_V”.
Basically, MSGL_DBG shouldn't create spam per frame like it currently
does, and MSGL_V should make sense to the end-user and provide mostly
additional informational output.

MP_DBG is basically what I want to make the new default for --log-file,
so the cut-off point for MP_DBG is if we probably want to know if for
debugging purposes but the user most likely doesn't care about on the
terminal.

Also, the debug callbacks for libass and ffmpeg got bumped in their
verbosity levels slightly, because being external components they're a
bit less relevant to mpv debugging, and a bit too over-eager in what
they consider to be relevant information.

I exclusively used the "try it on my machine and remove messages from
MSGL_* until it does what I want it to" approach of refactoring, so
YMMV.
2017-12-15 22:28:47 -08:00
..
cmd_list.c input: remove a stray HAVE_GPL 2017-11-29 18:28:27 +01:00
cmd_list.h input: drop deprecated "osd" command 2017-07-21 20:02:58 +02:00
cmd_parse.c
cmd_parse.h
event.c Use - as command-name separator everywhere 2016-07-14 22:37:42 +02:00
event.h
input.c msg: reinterpret a bunch of message levels 2017-12-15 22:28:47 -08:00
input.h input: merge mouse wheel and axis keycodes 2017-09-03 20:31:44 +10:00
ipc-dummy.c build: change how some OS specific source files are selected 2017-06-29 10:30:16 +02:00
ipc-unix.c ipc: avoid dereferencing NULL 2017-12-15 12:51:16 +02:00
ipc-win.c
ipc.c
keycodes.c input: merge mouse wheel and axis keycodes 2017-09-03 20:31:44 +10:00
keycodes.h input: fix error in MP_KEY_IS_WHEEL 2017-09-03 20:46:06 +10:00
pipe-win32.c