On Sun, Dec 16, 2012 at 12:57 PM, Tom Hacohen <[email protected]> wrote: > Hey Gustavo, > > Sorry for the delay. I'll be brief as I don't have much time or energy. :) > If you have any further questions, please feel free to ask. > If I remember correctly, there are two structures: > 1. Evas_Text_Props_Info > 2. Evas_Text_Props > > The first one is immutable and is refcounted. The second one is mutable and > everything goes with it. I guess the lack of a const before > Evas_Text_Props_Info *info is confusing, and I think it's an oversight. The > *_Info one includes all the info about the glyphs of a run, while the other > one represents a part of that run and points to the relevant info. > > With that being said, this code has changed since I touched it (some > adjustments were made by cedric iirc) so my info may be out of date.
Hi Tom, We mostly figured out that and we introduced some changes that will turn "glyphs" array into a structure with its length and refcount, not reusing that array anymore, we unref the old and create a new one (later we can optimize by recycling memory). One thing that was not clear to me (maybe the team figured out) is how the glyphs information and bitmaps are managed. When these data are released? How can we lock that if we have threads rendering in the background? BR, -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -------------------------------------- MSN: [email protected] Skype: gsbarbieri Mobile: +55 (19) 9225-2202 ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
