Lines Matching refs:jpeg_consume_input

2002 output.  This is done by calling the routine jpeg_consume_input().
2015 The library's output processing will automatically call jpeg_consume_input()
2017 display requires no direct calls to jpeg_consume_input().  But by adding
2018 calls to jpeg_consume_input(), you can absorb data in advance of what is
2025 jpeg_consume_input() with your display operations and any other processing
2027 call jpeg_consume_input() only after a hundred or so new bytes have arrived.
2029 library currently is not thread-safe.  You must not call jpeg_consume_input()
2040 jpeg_consume_input() repeatedly until it returns JPEG_SUSPENDED or
2045 jpeg_consume_input() whenever the current input scan number and row within
2066 through the image, jpeg_consume_input() will store data into the buffered
2086             absorb any waiting input by calling jpeg_consume_input()
2098             absorb any waiting input by calling jpeg_consume_input()
2116 from jpeg_consume_input(), or equivalently by testing jpeg_input_complete().)
2138 quickly.  To skip to the next scan, call jpeg_consume_input() until it
2154   (But it reads no input if jpeg_consume_input() has already reached the
2268 It is also worth noting that when you use jpeg_consume_input() to let input
2278 In some applications it may be convenient to use jpeg_consume_input() for all
2280 wish to call jpeg_consume_input() instead of jpeg_read_header() during
2284 jpeg_start_decompress() before jpeg_consume_input() will consume more input;
2286 tables-only file this way, jpeg_consume_input() will return JPEG_REACHED_EOI
2289 jpeg_abort() to reset it.  It is OK to call jpeg_consume_input() even when not