mpv - a free, open source, and cross-platform media player

	Commit message (Collapse)	Author	Age	Files	Lines
*	spelling fixes	Alessandro Ghedini	2013-10-20	1	-3/+3
\|
*	osc: fix borked options	ChrisK2	2013-10-15	1	-13/+13
\|
*	osc docs: Add documentation for OSC and rename some options	ChrisK2	2013-10-15	1	-6/+6
\| \| \| \|	camelCase from some of the option names removed. If you were using those, you'll have to update them in your config.
*	osc: reset mouse position when leaving window	ChrisK2	2013-10-15	1	-4/+9
\| \| \| \|	and store it freshly on first mouse_move event when entering again
*	osc: Don't create a config if none exists.	ChrisK2	2013-10-15	1	-19/+14
\| \| \| \|	A documentation explaing where and how to create one instead will follow.
*	osc: use "info" instead of "warn" for config file creation message	wm4	2013-10-14	1	-1/+1
\| \| \| \| \|	When the main mpv config file, "info" is used, so this makes things consistent.
*	osc: raise minmousemove default setting to 3 and disable input mouse area ↵	ChrisK2	2013-10-14	1	-6/+11
\| \| \| \| \| \|	when OSC not visible The mouse area that covers the OSC is now only activated when the OSC is actually visible, to make sure the mouse still hides if it happens to be parked in the OSC area without making the OSC show up.
*	osc: fix mouse hiding	ChrisK2	2013-10-13	1	-2/+2
\|
*	osc: Once again new Show/Hide handling	ChrisK2	2013-10-13	1	-7/+34
\| \| \| \| \| \| \|	The deadzone-size is now by default zero, so movement on the entire window will make the OSC show up. To avoid it showing up by randomly moving mice, the option 'minmousemove' controls how many pixels movement (default: 1) between ticks (frames) are necessary to make the OSC show up. The deadzone can be reenabeled by setting the option 'deadzonesize' (default: 0 = no deadzone, 1 = entire area between OSC and opposite window border), to restore the old behavior, set it to ~0.92. The OSC will hide immediately when leaving the window or entering the deadzone (if existing) or after the time specified with 'hidetimeout' (default: 500ms) passed without any new movement. Set to negative value to disabling auto-hide (thus restoring old behavior). The OSC will never hide if hovered by the mouse.
*	osc: Okay, don't multiply the cache value	ChrisK2	2013-10-07	1	-5/+1
\| \| \| \|	As expected, this is not liked.
*	osc: Display cache fill status	ChrisK2	2013-10-07	1	-1/+21
\| \| \| \| \| \|	The OSC will now display cache fill status between the timecodes, but only if it's below 48% to not clutter the interface with erratically changing values. By default, the displayed value is multiplied by 2 to not confuse users who are unfamillar with the inner workings of the caching system. This can be disabled using the iAmAProgrammer=true setting.
*	osc: Add another scale option for forced windows.	ChrisK2	2013-10-06	1	-3/+6
\| \| \| \|	If the OSC is rendered on a forced window (by --force-window), the scale can be configured with scaleForcedWindow.
*	osc: add options to show OSC only when FS/windowed	ChrisK2	2013-09-27	1	-2/+12
\| \| \| \| \| \|	The boolean-options showWindowed and showFullscreen can now be set in plugin_osc.conf to control the behaviour. enhancement for #262
*	osc: Prevent OSD style options from messing with the OSC styles	ChrisK2	2013-09-26	1	-18/+30
\| \| \| \|	Should fix #259
*	Add the on-screen-controller	ChrisK2	2013-09-26	1	-0/+1168
\| \| \| \|	Signed-off-by: wm4 <wm4@nowhere>
*	Add initial Lua scripting support	wm4	2013-09-26	2	-0/+180
	This is preliminary. There are still tons of issues, and any aspect of scripting may change in the future. I decided to merge this (preliminary) work now because it makes it easier to develop it, not because it's done. lua.rst is clear enough about it (plus some sarcasm). This requires linking to Lua. Lua has no official pkg-config file, but there are distribution specific .pc files, all with different names. Adding a non-pkg-config based configure test was considered, but we'd rather not. One major complication is that libquvi links against Lua too, and if the Lua version is different from mpv's, you will get a crash as soon as libquvi uses Lua. (libquvi by design always runs when a file is opened.) I would consider this the problem of distros and whoever builds mpv, but to make things easier for users, we add a terrible runtime test to the configure script, which probes whether libquvi will crash. This is disabled when cross-compiling, but in that case we hope the user knows what he is doing.