summaryrefslogtreecommitdiffstats
path: root/libass
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2015-12-31 16:28:00 +0100
committerwm4 <wm4@nowhere>2015-12-31 17:26:32 +0100
commit59f858b22477a02f835b6464928f28e4aaf38baa (patch)
tree7da0ccfd7b7a8cd31eec7cec906a6ade7789af32 /libass
parent9b87d1999fd7a3588bbcedddeab47f0bef34ac88 (diff)
downloadlibass-59f858b22477a02f835b6464928f28e4aaf38baa.tar.bz2
libass-59f858b22477a02f835b6464928f28e4aaf38baa.tar.xz
ass: declare mixing ass_flush_events() and ass_process_chunk() allowed
This was always the intention, but the wording could be read as if this is not allowed. There was a bug that broke ass_flush_events() too, which gives all the more reason to clarify this.
Diffstat (limited to 'libass')
-rw-r--r--libass/ass.h3
1 files changed, 2 insertions, 1 deletions
diff --git a/libass/ass.h b/libass/ass.h
index d3bf606..c2802f7 100644
--- a/libass/ass.h
+++ b/libass/ass.h
@@ -565,7 +565,8 @@ void ass_process_codec_private(ASS_Track *track, char *data, int size);
* In later libass versions (since LIBASS_VERSION==0x01300001), using this
* function means you agree not to modify events manually, or using other
* functions manipulating the event list like ass_process_data(). If you do
- * anyway, the internal duplicate checking might break.
+ * anyway, the internal duplicate checking might break. Calling
+ * ass_flush_events() is still allowed.
* \param track track
* \param data string to parse
* \param size length of data