Lines Matching refs:after
145 IDAT chunks and another (called "end_info" below) for things after them.
545 called after each row has been read, which you can use to control
667 You should put this statement after you create the PNG structure and
694 chunks after decompression). You can change this limit with
841 png_set_alpha_mode() - if you call it after it will override the settings made
911 If you call png_set_gamma() after png_set_alpha_mode() you
1118 errors it is therefore much safer to call png_set_background after the head has
1511 after decompression, 0 for iTXt
1514 after decompression, 0 for tEXt/zTXt
1686 There is also no requirement to have text after the keyword.
1696 However, some or all of the text chunks may be after the image, so, to
1698 until after you read the stuff after the image. This will be
1729 is called to insert filler bytes, either before or after each RGB triplet.
1735 or after each RRGGBB triplet. Similarly, 8-bit or 16-bit grayscale data can
1853 alpha channel (or the tRNS chunk data) after it's read, so that 0 is
1894 you want the filler before the RGB or after. When filling an 8-bit pixel,
1956 later check whether the image really was gray, after processing
1987 libpng-1.5.4 it is recommended that you call the function after reading the file
2117 after all of the other transformations have been processed. Take care with
2274 If you are not going to display the image after each pass, but are
2278 after each pass, the "rectangle" effect is generally considered the
2399 chunks after the image data, you can call png_set_crc_action()
2403 before or after the image data, you should pass the separate png_info
2404 struct if you want to keep the comments from before and after the image
2420 If you do this, libpng will not process any chunks after IDAT other than
2427 left pointing to the first chunk after the last IDAT, which is probably
2483 You can call this function after reading the PNG data but before calling
2486 and again after the png_set_*() functions to control whether the user
2640 png_read_update_info() after all the
2716 /* This function is called after the whole image
2717 has been read, including any chunks after the
2842 called after each row has been written, which you can use to control
2904 and then add and remove them after the start of compression.
2944 are allowed to write after the image is the text chunks and the time
2948 data as being valid. If you want to wait until after the data, don't
3152 after decompression, 0 for iTXt
3154 after decompression, 0 for tEXt/zTXt
3234 PNG_AFTER_IDAT: after IDAT
3238 You can change its value after calling png_set_unknown_chunks()
3294 some text before the image and some after. For example, you may want
3296 disclaimer until after, so viewers working over modem connections
3370 * one before IDAT and another after IDAT, so don't use it; only use
3445 be changed, and you can safely do this transformation after your
3583 or automatically after a certain number of lines have been written. To
3588 and to have libpng flush the output stream periodically after a certain
3758 You can call this function before calling after the png_set_*() functions
4086 NOTE: the flag can only be set after the png_image_begin_read_ call,
4137 after the structure is initialized.
4293 functions after png_create_*_struct() has been called by calling:
4319 after a longjmp, so the user may want to be careful about doing anything
4320 after setjmp returns non-zero besides returning itself. Consult your
4383 (Z_BEST_SPEED = 1). With versions of zlib after v0.99, you can also
4783 after the png_malloc() to set the pointers to NULL, to give robust.
4840 This statement must appear after png_read_png() or png_read_image() while
4841 reading, and after png_write_png() or png_write_image() while writing.
4861 directive. It does not matter whether this is placed prior to or after
5101 directive. It does not matter whether this is placed prior to or after
5165 transform after it calls png_read_update_info() or if it attempts to call
5318 Very short comments can be placed after the end of the statement
5365 We put a space after the "sizeof" operator and we omit the
5379 We put a space after each comma and after each semicolon
5380 in "for" statements, and we put spaces before and after each
5381 C binary operator and after "for" or "while", and before