The default fonts were changed, now Bitmap StrikeFonts are used instead of a TrueType font. Thus, the rendering method is completely different, and the use in StrikeFont rendering of some BitBlt methods revealed bugs in the alpha channel handling in said methods that previously went unnoticed. (Thus an updated VM/BitBlt plugin in required for them to render correctly).
Cheers, Henry On Dec 8, 2009, at 4:27 44PM, Hernan Wilkinson wrote: > but why the previous verson of pharo worked fine? there must be > something different in this new image... > > 2009/12/8 laurent laffont <laurent.laff...@gmail.com>: >> Hi, >> I had the same issue with exupery vm. Works with VM Squeak-3.11.3.2135. >> See: http://n2.nabble.com/New-pharo-images-td4125021.html#a4125467 >> Laurent >> >> 2009/12/8 Hernan Wilkinson <hernan.wilkin...@gmail.com> >>> >>> Hi, >>> the last version's fonts look really bad. See attached files >>> I have Ubuntu 9.10, 64 bits. >>> Dev09.11.4 looks fine >>> Maybe is a preference setting? >>> Hernan >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project@lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project@lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project@lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
