What exactly is the problem?
You need to pass paths to the library folders to compiler.
Checkout section Using Library/Install and Compile in Imaging's documentation for FPC compiler setup.

You don't need ImagingExtras  for Graphics32 interface, that's only for auto-include of extra file format handlers. Adding ImagingGraphics32 should be enough. Maybe try putting it into Source directory directly and see if it will be found by Delphi there.

Thanks!

Ok great.
Let me know if there are any more Imaging <=> Graphics32 interactions you may need
that are not supported by the current interface.

Binaries generated by Delphi are unfortunately quite often flagged by antivirus software as potentially containing mallware.

Sometimes even just empty projects are flagged:
http://stackoverflow.com/questions/1953817/anyone-having-problems-with-delphi-2010-and-norton-internet-security-2010
http://stackoverflow.com/questions/2185195/my-applications-auto-update-utility-is-triggering-anti-virus
...

I've changed the repository settings so now you can download revisions as zip or tar.gz archive
directly from Mercurial browser at SourceForge.
There are new links at the end of the top menu:
summary | shortlog | changelog | graph | tags | branches | files | zip | gz

You can post source code with syntax highlighting using [code=lang]your code[/code] tags. For Delphi/Pascal use [code=delphi] or [code=pascal].

Result looks like this:

procedure AddOne(var I: Integer);
begin
  I := I + 1;
end;

Imaging's source code repository at SourceForge has been migrated from Subversion to Mercurial.
Subversion repository will still be updated for some time (probably till 0.80 release).

To access the new repository use this address:
http://imaginglib.hg.sourceforge.net:8000/hgroot/imaginglib/imaginglib

Link to Imaging's Mercurial overview page at SF.net

Hi,

resizing image and reading center pixel is a good idea but you can do it faster:
Resizing with filtering basically computes average color for certain area of pixels
bu also reallocates memory, uses fancy filters, etc. You can do the averaging manually, just read some
pixels from the area you're interested in and compute the average color.

To get it even faster don't sample every pixel, but say every 3rd (maybe depending on the size of source image). Also read the pixels directly using pointers when you know the images will be all be in the same data format (usually 24bit RGB) or in just few formats.

There are TIFF tags PHOTOMETRIC_MINISBLACK and PHOTOMETRIC_MINISWHITE
which tell the decoder if pixel with value 0 is black or white.
Look's like Imaging does not set the tag for binary images and the decoder programs
assume some default. The default for Irfan and MS Imaging is probably different.
I'll update the TIFF writer to set the tag explicitly.

EDIT: So it looks like there's some bug in MS Office Document Imaging that ignores the
PHOTOMETRIC_MINISBLACK tag. Binary images are always assumed to be PHOTOMETRIC_MINISWHITE.
Other MS programs (Paint, Explorer, ...) handle binary TIFFs saved by Imaging correctly.

Hi, TIFF support in Imaging is provided by LibTiffDelphi library that uses precompiled
libtiff C library. Unfortunately, that's only available for Delphi.
There's test version of GCC compiled libtiff for Imaging in this thread that's usable in Lazarus.

Could you upload that fixed APNG? It would be helpful if I could see the internal differences
between the original from Imaging and the one that works in FF 3.6. Thanks

It looks ok in Firefox 4, maybe some bug in 3.6?
Is the first frame ok and the others garbled or everything is garbled?

Hi, it should be quite easy to convert TImageData to CMBitmap:

CMBitmap.image is TImageData.Bits
Width and Height is easy
CMBitmap.pixelSize is 8 * Fmt.BytesPerPixel (use GetImageFormatInfo function to get this)
CMBitmap.rowBytes is Width * CMBitmap.pixelSize

Then you need to set CmBitmap.space according to TImageData.Format,
mostly cmRGB24Space or cmRGBA32Space is used.

Hi, could you attach some of the APNGs that cause problems to this post?

Imaging is dual licensed LGLP and MPL. For commercial project it's simpler to choose MPL,
I added LGPL just to make Imaging compatible with GPL projects.

There's a nice explanation of MPL usage on Asphyre page: http://dev.ixchels.net/forum/faq.php?faq=asphyre_license