I see the time argument. Although, I would prefer waiting longer and going without the DLL solution.

There are so many libraries out there coming with DLLs and up to now Vampyre Imaging is the only with no need of a DLL so far as I know. It would be great if it stays so, also because of platform independence reasons (DLL is Windows only and any program I have written in Lazarus was compiling on Linux without any changes) and especially for little tools coming without an installer.

But of course, you are the developer, its your choice. I even cannot imagine how complex WebP is...

Do you mean that you would need an external DLL file to work with WebP?

I think one of the main advantages of Imaging is that you do not need external files and you get only one exe file. That is also one of the main reasons speaking for your library. I hope you will not change that...

Great to hear that!

I will have a look at this contribution. Is it working for FPC or is it still in progress?

Please tell if you need some more help.

Are there any plans to add support for the WebP Image File Format?

It seems as if this format is getting more and more important since it is increasingly used in websites.

At the top of the page http://imaginglib.sourceforge.net/ there is also stated:

QuoteGet the latest source code from Mercurial repository. Latest release version is 0.26.4 released on 12th October 2009. Get the library package in 7z or ZIP format: Imaging.7z | Imaging.ZIP.

This implies that the project has not been updated since 2009, which is not true. That can also discourage new users which would be very pity.

Quote from: JernejL on 17 May 2018, 10:15:04
Even if it was last updated in 2012, this library is so solid and productive it could well have no updates for years :)

Yes, of course! That is exactly what I also think. It's a great library!

I thought about the people that are seeing the page for the first time. And they could be discouraged from using the great lib because they thing that there is nobody working on it anymore. If there is stated a current date, they would not think so.

One little suggestion:

Your website available on http://imaginglib.sourceforge.net/ indicates that the project has not been continued since 2012.

I would update the date to 2018, otherwise users would think that the project is dead.

When loading an animated multiframe GIF with the function LoadMultiImageToFile and save it with SaveMultiImageToFile, the playback speed of the frames set in the original file is ignored. Instead, it is always set a time of 65/100 second.

I am using the newest version of Vampyre Imaging Library, default branch from sourceforge with FPC Lazarus.

Is there any possibility to save or set the delay?