20 Aug
2014
20 Aug
'14
8:02 a.m.
Hi,
My guess is that you took a Pharo image and then loaded Moose in it without
installing the Moose settings. Correct?
In that case, it is correct that it is a known bug. The issue is that Pharo
comes with StrikeFonts installed, and Roassal needs FreeTypeFont. That is
one of the reasons we use:
GTImageSetupCommandLineHandler new activateWithoutSaving.
Cheers,
Doru
On Wed, Aug 20, 2014 at 2:30 AM, Sean P. DeNigris <sean(a)clipperadams.com>
wrote:
In freshly downloaded Moose latest, opening the
Roassal Easel from the
world
menu -> MNU StrikeFont>>#glyphRendererOn:. Known bug?
-----
Cheers,
Sean
--
View this message in context:
http://forum.world.st/Roassal-Easel-Red-X-of-Death-tp4773878.html
Sent from the Moose mailing list archive at Nabble.com.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Every thing has its own flow"