When I try to localize an application that uses a TPngImageList component, the Resource DLL Wizard throws an error on the binary PNG data in the DFM. If I instead use a normal TImageList component the image data isn't even shown or processed by the Resource DLL Wizard. Does the Resource DLL Wizard have some magic here and understands that it should avoid to localize Image data on a TImageList component? If not, what is causing this behaviour?
My first thought was that the TPngImageList is saving the image data in some strange way in the DFM stream, but I cant find where or how..
I really lack in understanding of the DFM streaming mechanism and I cant find any good information about it. Would be great if someone could explain the basics of DFM streaming and also give some ideas why the Resource DLL Wizard tries to localize the TPngImageList image data, while it skips image data for a normal TImageList component.
Start Free Trial