I'd like to see a Lazarus package with only the base features (loading images, manipulating image data).
The visual features/LCL integration should go in another package that depends of the base package.

What is the advantage of this schema?

- Allowing other graphical toolkits like fpgui (http://opensoft.homeip.net/fpgui/) use imaging
- Allowing LCL components that uses only image loading features to be used in currently unsupported widgetsets like Qt and Carbon

I developed an LCL component that uses Imaging to load the images but don't use Imaging functions for the display. Since visual functions of Imaging does not compiles with Qt i created such "base" package and already uses it, but i'd like to see in the Imaging distribution.

Attached is the base and the visual packages. The only difference to users is that is needed to load the vampyreimaging_base package before installing vampyreimagingpackage.

When i have imaging 0.24.2 installed with Lazarus from svn under gtk the display of png files is wrong (As example the images in component palete of the ide are messed).

If i comment the RegisterTypes call in ImagingComponents unit the problem is gone.

Trying to compile imaging from svn with Lazarus from svn (rev 14368) under gtk gives an error due to internal changes in gtk widgetset.

Attached patch fixes it.

I have installed Imaging 0.24.2 in a recent Lazarus from svn (rev 14810) under Windows.

When i load a bitmap file into a image list using the image list editor the transparency does not work even if i load the project in a machine where vampyre is not installed.

If i comment RegisterTypes in ImagingComponents unit and rebuild Lazarus the transparency works again.

To a test application and more info see the bug report at http://bugs.freepascal.org/view.php?id=11150