Lines Matching refs:suspending

420   * If you use a suspending data destination manager, output buffer overrun
579   * A suspending data source is used --- in that case jpeg_read_header()
679 If you don't use a suspending data source, it is safe to assume that
1616 convenient restart point before suspending.  When fill_input_buffer() is
1637 common case where a non-suspending source manager is used.)
1640 and insert dummy EOI markers just as a non-suspending data source manager
1645 though it had read more data in a non-suspending situation.
1751 multiple-scan output cannot be created with a suspending data destination
1763 decoding application.  However, existing applications that used suspending
1850 (JPEG_SUSPENDED can occur only if a suspending data source is used.)  This
1992   was able to produce before suspending.
2003 and repeat the call.  Applications that use non-suspending data sources need
2092 to consume input as it makes this pass.  If you use a suspending data source,
2289 JPEG_SUSPENDED, is possible when using a suspending data source manager.)
2364 using a suspending data destination module.  In any case, if you are using
2365 a suspending destination, you should flush its buffer after inserting
2386 The first method is simpler to use, especially if you are using a suspending
2453 using a suspending data source and it tells you to suspend.  See the standard
2455 use a suspending data source.)
2628 If you use a suspending data source, jpeg_read_coefficients() will return
2631 non-suspending data source.