Lines Matching refs:jpeg_consume_input

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 adding
1859 calls to jpeg_consume_input(), you can absorb data in advance of what is
1866 jpeg_consume_input() with your display operations and any other processing
1868 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 or
1886 jpeg_consume_input() whenever the current input scan number and row within
1907 through the image, jpeg_consume_input() will store data into the buffered
1927 	    absorb any waiting input by calling jpeg_consume_input()
1939 	    absorb any waiting input by calling jpeg_consume_input()
1957 from jpeg_consume_input(), or equivalently by testing jpeg_input_complete().)
1979 quickly.  To skip to the next scan, call jpeg_consume_input() until it
1995   (But it reads no input if jpeg_consume_input() has already reached the
2109 It is also worth noting that when you use jpeg_consume_input() to let input
2119 In some applications it may be convenient to use jpeg_consume_input() for all
2121 wish to call jpeg_consume_input() instead of jpeg_read_header() during
2125 jpeg_start_decompress() before jpeg_consume_input() will consume more input;
2127 tables-only file this way, jpeg_consume_input() will return JPEG_REACHED_EOI
2130 jpeg_abort() to reset it.  It is OK to call jpeg_consume_input() even when not