diff options
Diffstat (limited to 'tqtinterface/qt4/src/3rdparty/libpng/libpng.txt')
| -rw-r--r-- | tqtinterface/qt4/src/3rdparty/libpng/libpng.txt | 78 |
1 files changed, 39 insertions, 39 deletions
diff --git a/tqtinterface/qt4/src/3rdparty/libpng/libpng.txt b/tqtinterface/qt4/src/3rdparty/libpng/libpng.txt index 60139c1..689b564 100644 --- a/tqtinterface/qt4/src/3rdparty/libpng/libpng.txt +++ b/tqtinterface/qt4/src/3rdparty/libpng/libpng.txt @@ -361,7 +361,7 @@ dithering, and setting filler.) If this is the case, simply do this: where png_transforms is an integer containing the logical OR of some set of transformation flags. This call is equivalent to png_read_info(), -followed the set of transformations indicated by the transform tqmask, +followed the set of transformations indicated by the transform mask, then png_read_image(), and finally png_read_end(). (The final parameter of this call is not yet used. Someday it might point @@ -535,12 +535,12 @@ into the info_ptr is returned for any complex types. png_get_tRNS(png_ptr, info_ptr, &trans, &num_trans, &trans_values); - trans - array of transtqparent entries for + trans - array of transparent entries for palette (PNG_INFO_tRNS) trans_values - graylevel or color sample values of - the single transtqparent color for + the single transparent color for non-paletted images (PNG_INFO_tRNS) - num_trans - number of transtqparent entries + num_trans - number of transparent entries (PNG_INFO_tRNS) png_get_hIST(png_ptr, info_ptr, &hist); @@ -773,7 +773,7 @@ is the level of opacity. If you need the alpha channel in an image to be the level of transparency instead of opacity, you can invert the alpha channel (or the tRNS chunk data) after it's read, so that 0 is fully opaque and 255 (in 8-bit or paletted images) or 65535 (in 16-bit -images) is fully transtqparent, with +images) is fully transparent, with png_set_invert_alpha(png_ptr); @@ -1212,8 +1212,8 @@ When you are done, you can free all memory allocated by libpng like this: It is also possible to individually free the info_ptr members that point to libpng-allocated storage with the following function: - png_free_data(png_ptr, info_ptr, tqmask, seq) - tqmask - identifies data to be freed, a tqmask + png_free_data(png_ptr, info_ptr, mask, seq) + mask - identifies data to be freed, a mask containing the logical OR of one or more of PNG_FREE_PLTE, PNG_FREE_TRNS, @@ -1231,7 +1231,7 @@ by the user and not by libpng, and will in those cases do nothing. The "seq" parameter is ignored if only one item of the selected data type, such as PLTE, is allowed. If "seq" is not -1, and multiple items are allowed for the data type identified in -the tqmask, such as text or sPLT, only the n'th item in the structure +the mask, such as text or sPLT, only the n'th item in the structure is freed, where n is "seq". The default behavior is only to free data that was allocated internally @@ -1239,8 +1239,8 @@ by libpng. This can be changed, so that libpng will not free the data, or so that it will free data that was allocated by the user with png_malloc() or png_zalloc() and passed in via a png_set_*() function, with - png_data_freer(png_ptr, info_ptr, freer, tqmask) - tqmask - which data elements are affected + png_data_freer(png_ptr, info_ptr, freer, mask) + mask - which data elements are affected same choices as in png_free_data() freer - one of PNG_DESTROY_WILL_FREE_DATA @@ -1274,8 +1274,8 @@ The png_free_data() function will turn off the "valid" flag for anything it frees. If you need to turn the flag off for a chunk that was freed by your application instead of by libpng, you can use - png_set_invalid(png_ptr, info_ptr, tqmask); - tqmask - identifies the chunks to be made invalid, + png_set_invalid(png_ptr, info_ptr, mask); + mask - identifies the chunks to be made invalid, containing the logical OR of one or more of PNG_INFO_gAMA, PNG_INFO_sBIT, @@ -1734,12 +1734,12 @@ Some of the more important parts of the png_info are: png_set_tRNS(png_ptr, info_ptr, trans, num_trans, trans_values); - trans - array of transtqparent entries for + trans - array of transparent entries for palette (PNG_INFO_tRNS) trans_values - graylevel or color sample values of - the single transtqparent color for + the single transparent color for non-paletted images (PNG_INFO_tRNS) - num_trans - number of transtqparent entries + num_trans - number of transparent entries (PNG_INFO_tRNS) png_set_hIST(png_ptr, info_ptr, hist); @@ -1955,7 +1955,7 @@ png_set_rows() to put image data in the info structure), simply do this: where png_transforms is an integer containing the logical OR of some set of transformation flags. This call is equivalent to png_write_info(), -followed the set of transformations indicated by the transform tqmask, +followed the set of transformations indicated by the transform mask, then png_write_image(), and finally png_write_end(). (The final parameter of this call is not yet used. Someday it might point @@ -1973,7 +1973,7 @@ Note that there is one transformation you may need to do before png_write_info(). In PNG files, the alpha channel in an image is the level of opacity. If your data is supplied as a level of transparency, you can invert the alpha channel before you write it, so -that 0 is fully transtqparent and 255 (in 8-bit or paletted images) or +that 0 is fully transparent and 255 (in 8-bit or paletted images) or 65535 (in 16-bit images) is fully opaque, with png_set_invert_alpha(png_ptr); @@ -1982,7 +1982,7 @@ This must appear before png_write_info() instead of later with the other transformations because in the case of paletted images the tRNS chunk data has to be inverted before the tRNS chunk is written. If your image is not a paletted image, the tRNS data (which in such cases -represents a single color to be rendered as transtqparent) won't need to +represents a single color to be rendered as transparent) won't need to be changed, and you can safely do this transformation after your png_write_info() call. @@ -2208,8 +2208,8 @@ When you are done, you can free all memory used by libpng like this: It is also possible to individually free the info_ptr members that point to libpng-allocated storage with the following function: - png_free_data(png_ptr, info_ptr, tqmask, seq) - tqmask - identifies data to be freed, a tqmask + png_free_data(png_ptr, info_ptr, mask, seq) + mask - identifies data to be freed, a mask containing the logical OR of one or more of PNG_FREE_PLTE, PNG_FREE_TRNS, @@ -2227,7 +2227,7 @@ by the user and not by libpng, and will in those cases do nothing. The "seq" parameter is ignored if only one item of the selected data type, such as PLTE, is allowed. If "seq" is not -1, and multiple items are allowed for the data type identified in -the tqmask, such as text or sPLT, only the n'th item in the structure +the mask, such as text or sPLT, only the n'th item in the structure is freed, where n is "seq". If you allocated data such as a palette that you passed @@ -2239,8 +2239,8 @@ by libpng. This can be changed, so that libpng will not free the data, or so that it will free data that was allocated by the user with png_malloc() or png_zalloc() and passed in via a png_set_*() function, with - png_data_freer(png_ptr, info_ptr, freer, tqmask) - tqmask - which data elements are affected + png_data_freer(png_ptr, info_ptr, freer, mask) + mask - which data elements are affected same choices as in png_free_data() freer - one of PNG_DESTROY_WILL_FREE_DATA @@ -2660,7 +2660,7 @@ A new feature in libpng 1.2.0 is the ability to dynamically switch between standard and optimized versions of some routines. Currently these are limited to three computationally intensive tasks when reading PNG files: decoding row filters, expanding interlacing, and combining interlaced or -transtqparent row data with previous row data. Currently the optimized +transparent row data with previous row data. Currently the optimized versions are available only for x86 (Intel, AMD, etc.) platforms with MMX support, though this may change in future versions. (For example, the non-MMX assembler optimizations for zlib might become similarly @@ -2677,32 +2677,32 @@ enable all possible optimizations (bearing in mind that some "optimizations" may actually run more slowly in rare cases): #if defined(PNG_LIBPNG_VER) && (PNG_LIBPNG_VER >= 10200) - png_uint_32 tqmask, flags; + png_uint_32 mask, flags; flags = png_get_asm_flags(png_ptr); - tqmask = png_get_asm_flagtqmask(PNG_SELECT_READ | PNG_SELECT_WRITE); - png_set_asm_flags(png_ptr, flags | tqmask); + mask = png_get_asm_flagmask(PNG_SELECT_READ | PNG_SELECT_WRITE); + png_set_asm_flags(png_ptr, flags | mask); #endif To enable only optimizations relevant to reading PNGs, use PNG_SELECT_READ -by itself when calling png_get_asm_flagtqmask(); similarly for optimizing +by itself when calling png_get_asm_flagmask(); similarly for optimizing only writing. To disable all optimizations: #if defined(PNG_LIBPNG_VER) && (PNG_LIBPNG_VER >= 10200) flags = png_get_asm_flags(png_ptr); - tqmask = png_get_asm_flagtqmask(PNG_SELECT_READ | PNG_SELECT_WRITE); - png_set_asm_flags(png_ptr, flags & ~tqmask); + mask = png_get_asm_flagmask(PNG_SELECT_READ | PNG_SELECT_WRITE); + png_set_asm_flags(png_ptr, flags & ~mask); #endif -To enable or disable only MMX-related features, use png_get_mmx_flagtqmask() -in place of png_get_asm_flagtqmask(). The mmx version takes one additional +To enable or disable only MMX-related features, use png_get_mmx_flagmask() +in place of png_get_asm_flagmask(). The mmx version takes one additional parameter: #if defined(PNG_LIBPNG_VER) && (PNG_LIBPNG_VER >= 10200) int selection = PNG_SELECT_READ | PNG_SELECT_WRITE; int compilerID; - tqmask = png_get_mmx_flagtqmask(selection, &compilerID); + mask = png_get_mmx_flagmask(selection, &compilerID); #endif On return, compilerID will indicate which version of the MMX assembler @@ -2711,7 +2711,7 @@ Visual C++ (compilerID == 1) and GNU C (a.k.a. gcc/gas, compilerID == 2). On non-x86 platforms or on systems compiled without MMX optimizations, a value of -1 is used. -Note that both png_get_asm_flagtqmask() and png_get_mmx_flagtqmask() return +Note that both png_get_asm_flagmask() and png_get_mmx_flagmask() return all valid, settable optimization bits for the version of the library that's currently in use. In the case of shared (dynamically linked) libraries, this may include optimizations that did not exist at the time the code was @@ -2743,8 +2743,8 @@ the png_mmx_support() function: It returns -1 if MMX support is not compiled into libpng, 0 if MMX code is compiled but MMX is not supported by the processor, or 1 if MMX support -is fully available. Note that png_mmx_support(), png_get_mmx_flagtqmask(), -and png_get_asm_flagtqmask() all may be called without allocating and ini- +is fully available. Note that png_mmx_support(), png_get_mmx_flagmask(), +and png_get_asm_flagmask() all may be called without allocating and ini- tializing any PNG structures (for example, as part of a usage screen or "about" box). @@ -2781,14 +2781,14 @@ certain extensions to PNG for PNG images that are embedded in MNG datastreams. Libpng can support some of these extensions. To enable them, use the png_permit_mng_features() function: - feature_set = png_permit_mng_features(png_ptr, tqmask) - tqmask is a png_uint_32 containing the logical OR of the + feature_set = png_permit_mng_features(png_ptr, mask) + mask is a png_uint_32 containing the logical OR of the features you want to enable. These include PNG_FLAG_MNG_EMPTY_PLTE PNG_FLAG_MNG_FILTER_64 PNG_ALL_MNG_FEATURES feature_set is a png_32_uint that is the logical AND of - your tqmask with the set of MNG features that is + your mask with the set of MNG features that is supported by the version of libpng that you are using. It is an error to use this function when reading or writing a standalone |