Lines Matching full:calling
11 The file example.c provides heavily commented skeleton code for calling the
135 The library emits compressed data by calling a "data destination manager",
157 The decompression library obtains compressed data by calling a data source
163 by calling jpeg_abort(); or, if you do not need to retain the JPEG object,
164 simply release it by calling jpeg_destroy().
256 variable in the calling routine, if a single routine is going to execute the
314 calling jpeg_start_compress() and jpeg_finish_compress().
337 calling jpeg_set_defaults(); then, if there are particular values you want
341 You must set in_color_space correctly before calling jpeg_set_defaults(),
344 jpeg_start_compress(). There's no harm in calling jpeg_set_defaults() more
382 Now write all the required image data by calling jpeg_write_scanlines()
466 When you are done with a JPEG compression object, destroy it by calling
491 legitimate at any point after calling jpeg_create_compress() --- in fact,
504 object that has reported an error by calling error_exit (see "Error handling"
559 You may not change the data source between calling jpeg_read_header() and
649 request large buffers *before* calling jpeg_start_decompress(). This is a
651 can make them valid by calling jpeg_calc_output_dimensions() after setting the
658 Now you can read the decompressed image data by calling jpeg_read_scanlines()
715 When you are done with a JPEG decompression object, destroy it by calling
726 You can abort a decompression cycle by calling jpeg_destroy_decompress() or
758 without recompiling the calling applications. That generally doesn't work
871 the JPEG color space is set correctly before calling this routine.
1204 space depending on in_color_space, but you can override this by calling
1292 This is accomplished by calling jpeg_std_error() as usual, but then overriding
1541 To use I/O suspension, cooperation is needed between the calling application
1548 responsible for emptying or refilling the work buffer before calling the
1590 before calling jpeg_finish_compress().
1663 memory, or skipped over by calling skip_input_data(). In the former case,
1843 output. This is done by calling the routine jpeg_consume_input().
1880 emptying the input buffer just before calling jpeg_start_output(): call
1927 absorb any waiting input by calling jpeg_consume_input()
1939 absorb any waiting input by calling jpeg_consume_input()
1999 calling jpeg_input_complete()).
2065 and colormap properly just before calling jpeg_start_output(). The following
2106 tested by calling jpeg_has_multiple_scans(), which will return a correct
2184 calling jpeg_start_compress() will prevent the table from being written at
2198 normally would, but instead of calling jpeg_start_compress() and so on, call
2349 calling jpeg_write_marker() after jpeg_start_compress() and before the first
2393 decompression object and before calling jpeg_read_header(), because the
2444 If you want to supply your own marker-reading routine, you do it by calling
2461 examination by calling jpeg_save_markers(); that method doesn't interfere
2506 jpeg_write_scanlines(). Before calling jpeg_start_compress(), you must do
2605 jpeg_read_header() as usual. But instead of calling jpeg_start_decompress()
2662 after calling jpeg_write_coefficients(). The data is actually written out
2680 individual sent_table flags, between calling jpeg_write_coefficients() and
