Searched refs:jpeg_consume_input (Results 1 – 9 of 9) sorted by relevance
250 retcode = jpeg_consume_input(cinfo); in jpeg_read_header()288 jpeg_consume_input (j_decompress_ptr cinfo) in jpeg_consume_input() function
42 #define jpeg_consume_input FOXIT_PREFIX(jpeg_consume_input) macro935 #define jpeg_consume_input jConsumeInput macro1062 EXTERN(int) jpeg_consume_input JPP((j_decompress_ptr cinfo));
932 #define jpeg_consume_input jConsumeInput macro1069 EXTERN(int) jpeg_consume_input JPP((j_decompress_ptr cinfo));
1843 output. This is done by calling the routine jpeg_consume_input().1856 The library's output processing will automatically call jpeg_consume_input()1858 display requires no direct calls to jpeg_consume_input(). But by adding1859 calls to jpeg_consume_input(), you can absorb data in advance of what is1866 jpeg_consume_input() with your display operations and any other processing1868 call jpeg_consume_input() only after a hundred or so new bytes have arrived.1870 library currently is not thread-safe. You must not call jpeg_consume_input()1881 jpeg_consume_input() repeatedly until it returns JPEG_SUSPENDED or1886 jpeg_consume_input() whenever the current input scan number and row within1907 through the image, jpeg_consume_input() will store data into the buffered[all …]
538 if the application calls jpeg_consume_input(); otherwise input and output550 case. jpeg_consume_input() is effectively a no-op in this situation.
META-INF/MANIFEST.MF META-INF/ECLIPSEF.SF META-INF/ECLIPSEF ...