Lines Matching refs:png_info

113 png_struct and png_info instances, and thus its own image.
120 and png_info.  Both are internal structures that are no longer exposed
123 The png_info structure is designed to provide information about the
124 PNG file.  At one time, the fields of png_info were intended to be
127 a set of interface functions for png_info (the png_get_*() and png_set_*()
128 functions) was developed, and direct access to the png_info fields was
136 to png_info as the second argument.  Some application visible macros
138 integers in the PNG format) don't take a png_info pointer, but it's almost
142 You can have more than one png_info structure associated with an image,
365 Next, png_struct and png_info need to be allocated and initialized.  In
2162 After setting the transformations, libpng can update your png_info
2402 before or after the image data, you should pass the separate png_info
2747 Next, png_struct and png_info need to be allocated and initialized.
2941 You now need to fill in the png_info structure with all the data you
2948 fill them until png_write_end().  For all the fields in png_info and
2952 Some of the more important parts of the png_info are:
3685 pass an appropriately filled png_info pointer.  If you are not interested,
4852 members of the main libpng control structures, png_struct and png_info,
5334  png_exported_function(png_ptr, png_info, foo)
5350  png_non_exported_function(png_ptr, png_info, foo)