Lines Matching refs:lodepng
2 LodePNG version 20131222
110 Return value: LodePNG error code (0 means no error).
159 Return value: LodePNG error code (0 means no error).
195 namespace lodepng
238 } //namespace lodepng
310 format, and is used both for PNG and raw image data in LodePNG.
326 When decoding, by default you can ignore this palette, since LodePNG already
340 When decoding, by default you can ignore this information, since LodePNG sets
497 return value = LodePNG error code (0 if all went ok, an error if the conversion isn't supported)
610 have to cleanup this buffer, LodePNG will never free it. Don't forget that filter_palette_zero
618 /*add LodePNG identifier and version as a text chunk, for debugging*/
643 //For the lodepng::State subclass.
821 //The LodePNG C++ wrapper uses std::vectors instead of manually allocated memory buffers.
822 namespace lodepng
835 //Same as other lodepng::decode, but using a State for more settings and information.
845 //Same as other lodepng::encode, but using a State for more settings and information.
890 } //namespace lodepng
905 [ ] let the C++ wrapper catch exceptions coming from the standard library and return LodePNG error codes
911 LodePNG Documentation
945 LodePNG is a PNG codec according to the Portable Network Graphics (PNG)
957 The most recent version of LodePNG can currently be found at
958 http://lodev.org/lodepng/
960 LodePNG works both in C (ISO C90) and C++, with a C++ wrapper that adds
963 LodePNG exists out of two files:
964 -lodepng.h: the header file for both C and C++
965 -lodepng.c(pp): give it the name lodepng.c or lodepng.cpp (or .cc) depending on your usage
967 If you want to start using LodePNG right away without reading this doc, get the
968 examples from the LodePNG website to see how to use it in code, or check the
971 LodePNG is simple but only supports the basic requirements. To achieve
980 This all makes LodePNG suitable for loading textures in games, demos and small
1020 *) The following public chunks are not supported but treated as unknown chunks by LodePNG
1022 Some of these are not supported on purpose: LodePNG wants to provide the RGB values
1034 lodepng::State class which is a LodePNGState with constructor and destructor.
1040 To use the C++ version, you need to rename the source file to lodepng.cpp
1041 (instead of lodepng.c), and compile it with a C++ compiler.
1043 To use the C version, you need to rename the source file to lodepng.c (instead
1044 of lodepng.cpp), and compile it with a C compiler.
1050 Even if carefully designed, it's always possible that LodePNG contains possible
1053 When using LodePNG, care has to be taken with the C version of LodePNG, as well
1072 various lodepng::decode functions, and lodepng::State can be used for advanced
1123 various lodepng::encode functions, and lodepng::State can be used for advanced
1180 *) add_id: add text chunk "Encoder: LodePNG <version>" to the image.
1190 An important thing to note about LodePNG, is that the color type of the PNG, and
1194 And if you encode an image, by default LodePNG will automatically choose the PNG
1199 To be able to do this, LodePNG does conversions from one color mode to another.
1210 LodePNG automatically picks the best color model for the output PNG, and expects
1221 decoding to have another color type, a conversion is done by LodePNG.
1243 or the parameters of the simple function of LodePNG you're using.
1247 of the raw image, or use the parameters of the simplefunction of LodePNG you're
1250 If, when encoding, you don't want LodePNG to choose the output PNG color type
1255 If you do any of the above, LodePNG may need to do a color conversion, which
1270 -even though some conversions aren't supported, LodePNG supports loading PNGs from any
1305 scanline starts at a fresh byte. But that is NOT true for the LodePNG raw input and output.
1314 LodePNG uses unsigned char arrays for 16-bit per channel colors too, just like
1319 LodePNG always uses big endian because the PNG file format does so internally.
1321 LodePNG on purpose, there are myriads of formats, including endianness of 16-bit
1323 converting to/from all that is outside the scope of LodePNG.
1326 endian output of LodePNG to little endian with a for loop. This is certainly not
1335 All functions in LodePNG that return an error code, return 0 if everything went
1338 The meaning of the LodePNG error values can be retrieved with the function
1348 If you want to add extra chunks to a PNG you encode, or use LodePNG for a PNG
1350 program is able to read other types of chunks than the ones handled by LodePNG,
1351 then that's possible with the chunk functions of LodePNG.
1441 If you need it to add a particular chunk that isn't known by LodePNG, you can
1445 Chunks that are known by LodePNG should not be added in that way. E.g. to make
1446 LodePNG add a bKGD chunk, set background_defined to true and add the correct
1454 LodePNG. For the C++ version, only the standard C++ library is needed on top.
1455 Add the files lodepng.c(pp) and lodepng.h to your project, include
1456 lodepng.h where needed, and your program can read/write PNG files.
1461 Make sure that LodePNG is compiled with the same compiler of the same version
1465 CHAR_BITS must be 8 or higher, because LodePNG uses unsigned chars for octets.
1469 LodePNG is developed in gcc so this compiler is natively supported. It gives no
1475 The Mingw compiler (a port of gcc) for Windows is fully supported by LodePNG.
1480 can't support the proposed Visual Studio alternative however, so LodePNG keeps using
1481 fopen. If you don't want to see the deprecated warnings, put this on top of lodepng.h
1485 Other than the above warnings, LodePNG should be warning-free with warning
1488 Studio use warning level W3 for lodepng.cpp only: right click lodepng.cpp,
1493 That is not standard C++ and will not be added to the stock LodePNG. You can
1494 disable it for lodepng.cpp only by right clicking it, Properties, C/C++,
1499 LodePNG support for Visual Studio 6.0 is not guaranteed because VS6 doesn't
1509 LodePNG has been reported to work both with the gcc and LLVM for Macintosh, both
1521 This decoder example shows the most basic usage of LodePNG. More complex
1522 examples can be found on the LodePNG website.
1527 #include "lodepng.h"
1537 unsigned error = lodepng::decode(image, width, height, filename);
1548 #include "lodepng.h"
1571 The version number of LodePNG is the date of the change given in the format
1582 use custom ones in your project without needing to change lodepng's code.
1629 *) 20 jan 2008: support for unknown chunks allowing using LodePNG for an editor.
1635 *) 07 jan 2008: (!) changed LodePNG to use ISO C90 instead of C++. A
1637 Having LodePNG be pure ISO C90 makes it more portable. The C and C++ code
1683 struct of type LodePNG::LodePNG_Info, instead of a vector, which was a bit clumsy.
1696 in LodePNG namespace. Changed the order of the parameters. Rewrote the
1697 documentation in the header. Renamed files to lodepng.cpp and lodepng.h
1707 LodePNG. If you encounter a PNG image that doesn't work properly with this
