Tudor Girba wrote:

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

Maybe a class initialize method that would load from the Configuration Browser item Roasal could display a dialog asking the user if they want to make the required Preference changes. It would be really good for Roassal to load cleanly into a base Pharo image. The other day I wanted to chase down some strong pointers and thought Roassal would be great for this, but it didn't work out of the box and so I resorted to rolling my own hack for this in Morphic. Now I would normally just sue Moose to use Roassal, except it was stuff in an existing image I wanted to graph.
cheers -ben

On Wed, Aug 20, 2014 at 2:30 AM, Sean P. DeNigris <sean@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@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--

www.tudorgirba.com

"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
  