mpv/libmpv
wm4 31c04f162b client API: be explicit about usage rules and deadlocks some more
I think a popular libmpv application did exactly this: enabling advanced
control, and then receiving deadlocks. I didn't confirm it, though. In
any case, the API docs should avoid tricking users into making this easy
mistake.
2019-09-26 14:17:00 +02:00
..
client.h client API: fix potential deadlock problems by throwing more shit at it 2019-09-26 14:14:49 +02:00
mpv.def client API: add mpv_command_ret 2019-09-21 14:24:42 +02:00
mpv.pc.in build: add hacks to force waf to generate valid .pc files 2014-08-07 23:45:40 +02:00
opengl_cb.h drm/atomic: add connector to atomic context 2018-05-01 20:48:02 +03:00
qthelper.hpp client API: deprecate qthelper.hpp 2018-03-15 23:13:53 -07:00
render.h client API: be explicit about usage rules and deadlocks some more 2019-09-26 14:17:00 +02:00
render_gl.h drm: fix libmpv ABI breakage introduced in 351c083487 2019-09-18 23:59:32 +03:00
stream_cb.h client API: some doxygen fixes/additions 2018-05-24 19:56:33 +02:00