Lines Matching full:manager
135 The library emits compressed data by calling a "data destination manager",
137 provide its own destination manager to do something else.
158 manager, which typically will read the data from a file; but other behaviors
159 can be obtained with a custom source manager. Decompressed data is delivered
420 * If you use a suspending data destination manager, output buffer overrun
423 stdio destination manager will NOT cause this to happen.
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.
581 below. The normal stdio source manager will NOT cause this to happen.
647 Note: if you are using the JPEG library's internal memory manager to allocate
648 data buffers (as djpeg does), then the manager's protocol requires that you
700 If using the stdio source manager, don't forget to close the source stdio
710 manager, the next image will be read from the same source.
768 critical if you are on MS-DOS and use the jmemdos.c memory manager back end;
775 if you replace those modules and use jmemnobs.c (or another memory manager of
1160 JPEG library's memory manager to allocate output buffer space, because you
1299 field). This struct includes a pointer to the error manager struct in its
1376 manager" module. The default destination manager just writes the data to a
1377 stdio stream, but you can provide your own manager to do something else.
1378 Similarly, the decompression library calls a "source manager" to obtain the
1379 compressed data; you can provide your own source manager if you want the data
1383 destination or source manager provides a work buffer, and the library invokes
1384 the manager only when the buffer is filled or emptied. (You could define a
1385 one-character buffer to force the manager to be invoked for each byte, but
1387 controlled by the manager, not by the library. For example, if you desired to
1399 A data destination manager struct contains a pointer and count defining the
1406 is filled. The manager's empty_output_buffer method must reset the pointer
1407 and count. The manager is expected to remember the buffer's starting address
1410 A data destination manager provides three methods:
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.
1446 additional frammishes. The source manager struct contains a pointer and count
1454 is emptied. The manager's fill_input_buffer method must reset the pointer and
1455 count. In most applications, the manager must remember the buffer's starting
1458 A data source manager provides five methods:
1513 the source manager to be cleaned up during an abort, you must do it yourself.
1519 jpeg_stdio_src() routine of the supplied source manager.
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
1627 The skip_input_data() source manager routine requires special care in a
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
1752 manager, since jpeg_finish_compress() does not support suspension. We
2112 manager jmemnobs.c if you can (ie, if you have enough real or virtual main
2114 possible. If the JPEG memory manager has to use a temporary file, you will
2116 improved with additional work on the memory manager, but we haven't gotten
2289 JPEG_SUSPENDED, is possible when using a suspending data source manager.)
2610 memory manager's access_virt_barray method (see Memory management, below,
2660 requested from the compression object's memory manager. Thus, when obtaining
2715 JPEG memory manager with lifetime JPOOL_PERMANENT will work nicely.) You
2755 manager. For more info, please read structure.doc's section about the memory
2756 manager, and consult the source code if necessary.
2759 memory manager. If necessary, you can replace the "back end" of the memory
2760 manager to control allocation yourself (for example, if you don't want the
2766 memory manager yourself to allocate structures that will automatically be
2781 If you use the simplest memory manager back end (jmemnobs.c), then no
2784 The other memory manager back ends support temporary files of various flavors
2800 If you use the jmemname.c or jmemdos.c memory manager back end, it is
2955 manager "back end" module, so you can use a different memory allocator by
