summaryrefslogtreecommitdiffstats
path: root/waftools
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2014-06-07 20:13:01 +0200
committerwm4 <wm4@nowhere>2014-06-07 20:13:01 +0200
commit0b9468f65f6014b888cdb1c5c473569ca8d9c57f (patch)
tree88d7e69fed9483661a73dc1943a41ff1bdff2fbd /waftools
parent500ce69a06be2cb2b79f310e638e4c4ceabe447e (diff)
downloadmpv-0b9468f65f6014b888cdb1c5c473569ca8d9c57f.tar.bz2
mpv-0b9468f65f6014b888cdb1c5c473569ca8d9c57f.tar.xz
client API: clarify mpv_get_wakeup_pipe docs
It wasn't necessarily clear how this works. Especially make clear that the API user shouldn't expect that there's one byte per readable event in the wakeup pipe. Actually, the reason why this currently won't work is because property notifications can generate more events than wakeups. The limit of 4096 is a more fundamental issue, but the event ringbuffer is currently limited to 1000 entries anyway. Also add some important comments to mpv_set_wakeup_callback.
Diffstat (limited to 'waftools')
0 files changed, 0 insertions, 0 deletions