Lines Matching full:destination
40 Compressed data handling (source and destination managers)
116 Specify the destination for the compressed data (eg, a file)
135 The library emits compressed data by calling a "data destination manager",
137 provide its own destination manager to do something else.
176 memory fashion, if suitable source/destination managers are used. See the
285 2. Specify the destination for the compressed data (eg, a file).
288 "data destination" module. The library includes one data destination
290 destination module if you want to do something else, as discussed later.
292 If you use the standard destination module, you must open the target stdio
303 where the last line invokes the standard destination module.
312 You can select the data destination after setting other parameters (step 3),
313 if that's more convenient. You may not change the destination between
360 destination and set all the necessary
420 * If you use a suspending data destination manager, output buffer overrun
423 stdio destination manager will NOT cause this to happen.
432 last bufferload of data is written to the data destination.
440 If using the stdio destination manager, don't forget to close the output
456 destination manager, the new datastream will be written to the same target.
499 Note that cleaning up the data destination, if required, is your
773 require the stdio library: only the default source/destination managers and
1372 Compressed data handling (source and destination managers)
1375 The JPEG compression library sends its compressed data to a "destination
1376 manager" module. The default destination manager just writes the data to a
1383 destination or source manager provides a work buffer, and the library invokes
1396 source and destination modules to transcribe the work arrays into 8-bit units
1399 A data destination manager struct contains a pointer and count defining the
1410 A data destination manager provides three methods:
1413 Initialize destination. This is called by jpeg_start_compress()
1430 Terminate destination --- called by jpeg_finish_compress() after all
1436 want the destination manager to be cleaned up during an abort, you must do it
1443 the jpeg_stdio_dest() routine of the supplied destination manager.
1521 For more information, consult the stdio source and destination managers
1531 be emptied or reloaded within the data source/destination manager subroutine.
1542 and the data source or destination manager; you will always need a custom
1543 source/destination manager. (Please read the previous section if you haven't
1751 multiple-scan output cannot be created with a suspending data destination
2210 set destination to tables-only file
2212 set destination to image file
2304 If you intend to write a series of images into a single destination file,
2305 you might want to make a specialized data destination module that doesn't
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
2369 you can just cram it straight into the data destination module.
2564 destination module suspends, jpeg_write_raw_data() will return 0.
2943 to redefine JOCTET and/or provide custom data source/destination managers so
2952 stdio is used only by the data source/destination modules and the error
