Hi BR. thanks.
i understand ,continue to dig the source. On Wed, 2010-05-12 at 23:08 -0300, Gustavo Sverzut Barbieri wrote: > 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, > > --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
