Just to avoid going in the tool issue again. Could you reproduce this problem on a plain Pharo3 + Roassal image? Then we can announce the image on the Pharo mailing list and see if we can get help.
In a 30851, with the 355 vm (Mavericks), opened a workspace,
Gofer new smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; package: 'ConfigurationOfRoassal2'; load. (Smalltalk at: #ConfigurationOfRoassal2) load
loaded an old version of Roassal2
If I open RoassalExamples in the world menu, I get a red window.
Opening the settings, unselecting and reselecting FreeType doesn't help. Setting the standard font to Helvetica Neue and using that as default font for everything makes Roassal2 work.
Stephan
Thanks, but that is not the bug we are talking about.
After loading the true type fonts (e.g., "Source Sans Pro" in the Moose image), you get problems when rendering labels in Athens using Roassal. Somehow this is not always reproducible. That is what we need to capture.
Cheers, Doru
On Mon, Jul 7, 2014 at 5:20 PM, Stephan Eggermont stephan@stack.nl wrote:
Just to avoid going in the tool issue again. Could you reproduce this
problem on a plain Pharo3 + Roassal image?
Then we can announce the image on the Pharo mailing list and see if we
can get help.
In a 30851, with the 355 vm (Mavericks), opened a workspace,
Gofer new smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; package: 'ConfigurationOfRoassal2'; load. (Smalltalk at: #ConfigurationOfRoassal2) load
loaded an old version of Roassal2
If I open RoassalExamples in the world menu, I get a red window.
Opening the settings, unselecting and reselecting FreeType doesn't help. Setting the standard font to Helvetica Neue and using that as default font for everything makes Roassal2 work.
Stephan
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Stephan Eggermont -
Tudor Girba