On Wed, May 12, 2010 at 10:48 PM, Dejun.Liu <[email protected]> wrote: > Hi. > > recently ,I dig the evas source code ,but i did not understand how image > cache works,so is there any docs on this subject?
Image cache should be transparent. Once you load the image the parameters are mangled into a hash table key and the contents in the data. As images are mostly read-only, unless told otherwise, these are shared among all possible users. If the last user goes away, then it is put into cache (it may the evas_object_image being deleted, or it being set to use another image), then this cache is limited to the number of bytes configured. If one ask the image pixels to be written, then the image is copied and these pixels are returned, so other users will not be affected. BR, -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -------------------------------------- MSN: [email protected] Skype: gsbarbieri Mobile: +55 (19) 9225-2202 ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
