Home | History | Annotate | Download | only in jpeg

Lines Matching full:want

9 program.  Read it if you want to write a program that uses the library.
262 are providing your own error handler, you'll typically want to embed the
290 destination module if you want to do something else, as discussed later.
335 image is encoded. Most applications don't need or want to know about all
337 calling jpeg_set_defaults(); then, if there are particular values you want
371 want to use an abbreviated datastream, read the section on abbreviated
390 terms (a curious interpretation of the English language...) but if you want
494 * If you want to re-use the JPEG object, call jpeg_abort_compress(), or call
536 to read from a stdio stream. You can use your own source module if you want
597 may well want to alter these defaults before beginning the decompression.
599 If you want colormapped output you must ask for it. Other options allow the
728 jpeg_abort_decompress() or jpeg_abort() if you want to reuse the object.
745 installing the JPEG header files in a system directory, you will want to
812 routine; if you want to twiddle individual parameters you should call
818 jpeg_set_defaults(). It's broken out in case you want to change
870 unless you want to make a custom scan sequence. You must ensure that
896 jpeg_set_color_space() if you want to change these.
918 If you use restarts, you may want to use larger intervals in those
1072 currently implemented; you may need to extend jdcolor.c if you want an
1123 Copy the colormap somewhere else first, if you want to save it.
1222 jpeg_color_space to JCS_YCbCr; use JCS_UNKNOWN. You may want to write an
1228 well want to change these parameters. See the source code for
1250 the code if you want to use it for non-RGB output color spaces. Note that
1379 compressed data; you can provide your own source manager if you want the data
1436 want the destination manager to be cleaned up during an abort, you must do it
1512 term_source() is NOT called by jpeg_abort() or jpeg_destroy(). If you want
1529 memory filter: when the compressed data buffer is filled or emptied, they want
1570 for efficiency; you don't want the compressor to suspend often. (In fact, an
1573 several Kbytes. You may want to insert explicit code to ensure that you don't
1744 applications that don't want to get involved in the nitty-gritty of
1745 progressive scan sequence design. (If you want to provide user control of
1836 you want special processing in the final pass.
1922 When using this strategy, you'll want to be sure that you perform a final
1936 for the final pass. But if you don't want to use special parameters for
1949 the final output pass; rather, what you want to test is whether the output
1969 file has arrived and you want to begin the final output pass immediately.
2046 probably NOT what you want for the first pass of progressive display!)
2068 or 2-pass mode from a different mode, or when you want the 2-pass
2073 NOTE: if you want to use the same colormap as was used in the prior pass,
2187 If you want to create a "pure" abbreviated image file containing no tables,
2189 tables. If you want to emit some but not all tables, you'll need to set the
2224 image...) Generally, you don't want to set optimize_coding = TRUE when
2227 In some cases you might want to compress an image using tables which are
2269 You might want to read the tables from a tables-only file, rather than
2285 In some cases, you may want to read a file without knowing whether it contains
2305 you might want to make a specialized data destination module that doesn't
2408 first few bytes of a potentially large marker. If you want to save all the
2426 common, however. If you are short on memory you may want to reset the length
2444 If you want to supply your own marker-reading routine, you do it by calling
2458 recognize JFIF and Adobe markers if you want colorspace recognition to occur
2460 want to do that. (A better idea is to save these marker types for later
2517 explicitly, rather than assuming the library's defaults are what you want.
2678 emitting abbreviated JPEG files by accident. If you really want to emit an
2704 you want fine resolution in the progress count. (If you really need to use
2760 manager to control allocation yourself (for example, if you don't want the
2882 You may also want to supply your own DCT quantization tables; the existing
2895 You probably don't want to make JSAMPLE be int unless you have lots of memory