Searched refs:jpeg_consume_input (Results 1 – 10 of 10) sorted by relevance
261 retcode = jpeg_consume_input(cinfo); in jpeg_read_header()299 jpeg_consume_input(j_decompress_ptr cinfo) in jpeg_consume_input() function
2009 output. This is done by calling the routine jpeg_consume_input().2022 The library's output processing will automatically call jpeg_consume_input()2024 display requires no direct calls to jpeg_consume_input(). But by adding2025 calls to jpeg_consume_input(), you can absorb data in advance of what is2032 jpeg_consume_input() with your display operations and any other processing2034 call jpeg_consume_input() only after a hundred or so new bytes have arrived.2036 library currently is not thread-safe. You must not call jpeg_consume_input()2047 jpeg_consume_input() repeatedly until it returns JPEG_SUSPENDED or2052 jpeg_consume_input() whenever the current input scan number and row within2073 through the image, jpeg_consume_input() will store data into the buffered[all …]
1017 EXTERN(int) jpeg_consume_input(j_decompress_ptr cinfo);
508 if the application calls jpeg_consume_input(); otherwise input and output520 case. jpeg_consume_input() is effectively a no-op in this situation.
299 `jpeg_consume_input()` would return `JPEG_SUSPENDED` rather than
41 jpeg_consume_input @ 40 ;
40 jpeg_consume_input @ 39 ;