On Dec 8, 2009, at 11:33 20AM, Mariano Martinez Peck wrote: > > > Thanks John. I am interested in your experience. However, I didn't understand > this last paragraph where you said to finally make it work. > I don't understand what did you change. What is the difference between "font > menu" and " stored forms of > each font face for the menu" ? The way I read it, instead of storing the fonts themselves in an image segment, they stored a form with a string rendered by the font, then used that to display in list instead of actually loading the font, and rendering text with it. That way the list could be shown fast, without having to load the fonts themselves until actually used/fonts on the machine changes. > > In addition, do you know why this has solved the problems ?
If you look at the relative complexity of TTCFont and Form instances, it'd hardly come as a surprise that one may be loaded consistently, while the other is harder to get loaded correctly in all cases... In other words, to me it seems like a workaround for non-repeatable errors when loading complex objects within ImageSegments (by storing simpler objects instead). Cheers, Henry _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
