>Date: Tue, 11 Oct 2005 09:59:24 +0300 >From: "Cosmin Prund" <[EMAIL PROTECTED]> >Subject: Re: Update TJpgImgList >To: "Borland's Delphi Discussion List" <[email protected]> >Message-ID: <[EMAIL PROTECTED]> >Content-Type: text/plain; format=flowed; charset="iso-8859-1"; >reply-type=original
>I've done a little math: you've loaded a 240x320 24bit BMP; The same amount >of space would be required to hold 300 16x16 images or 133 24x24 images. Your math is correct.... >I think you're kind of miss-using MS's TImageList if you add large (240x320 >is large) images to it. This control is designed to efficiently hold SMALL >images (16x16 / 24x24 / 32x32) - the kind of images one usually uses for >menus and toolbar buttons. It's deffinitivley NOT a repository for >splash-screen-sized images! Deffinately NOT useful for images over 96 x 96 Holding small images the control works rather well with 180 + 16x16 bmp's... >Again, given it's purpuse, it's only natural it only holds BMP's. If it >would hold JPG's it would probably need to turn them into BMP at run time >and cache them any way. Also I don't think a 16x16 256 colors bitmap would >compress very well when turned into a JPG. You are correct again, it wouldn't compress well... >One last thing: While the increase in your exe size is difficult to >understand, the increased COMPILE time has nothing to do with TImageList >and >has allmost everything to do with Borland's DFM files! You'll have the SAME >problem trying to store 5,6 Mb of ANYTHING into a DFM! (Guess DFM was not >designed as a file repository...) The imagelist data is stored in your exe file is why exe size grew :) Thanks for pointing out some interesting points to ponder on... I've learned that imagelist is useful given it's not used to store images greater than 96 x 96 Some things are learned the hard way trial and error :p Kind Regards Eric Daniels _______________________________________________ Delphi mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi
