summaryrefslogtreecommitdiffstats
path: root/demux
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2019-09-26 14:09:14 +0200
committerwm4 <wm4@nowhere>2019-09-26 14:17:00 +0200
commit31c04f162b8c7bfaed7f76eaa18da3c4f41c090e (patch)
treeda069482c49e3d8211688dab000a496d160fb4dd /demux
parent4d43c79e4c1b76d70bf0e976e6c72945ce962140 (diff)
downloadmpv-31c04f162b8c7bfaed7f76eaa18da3c4f41c090e.tar.bz2
mpv-31c04f162b8c7bfaed7f76eaa18da3c4f41c090e.tar.xz
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.
Diffstat (limited to 'demux')
0 files changed, 0 insertions, 0 deletions