On Sun, Aug 09, 2009 at 03:59:25PM -0400, Art Hunkins wrote:
This happens on all text (i.e., not-image) display, to my knowledge.
Obvious examples are the Log and Terminal Activities.
The most problemmatic examples are when text is used in a PyGTK boxed
context (such as the 4 activities
Aleksey,
To clarify my bug: SoaS text is not just too small in a given Activity;
text is too small in SoaS *overall*.
SoaS's default font size seems to be 10 - the same as for XO-1. Any text
that SoaS prints seems to be size 10. For me to get readable text, I need to
raise all instances (in
On Tue, Aug 11, 2009 at 12:32 PM, Art Hunkinsabhun...@uncg.edu wrote:
Aleksey,
To clarify my bug: SoaS text is not just too small in a given Activity;
text is too small in SoaS *overall*.
SoaS's default font size seems to be 10 - the same as for XO-1. Any text
that SoaS prints seems to be
This happens on all text (i.e., not-image) display, to my knowledge.
Obvious examples are the Log and Terminal Activities.
The most problemmatic examples are when text is used in a PyGTK boxed
context (such as the 4 activities included in Victor Lazzarini's csndsugui
project).
Basically text
I am curious as to how Turtle Art behaves in your tests. (I include a
scaling factor which is different for non-OLPC-XO displays.)
-walter
On Sun, Aug 9, 2009 at 3:59 PM, Art Hunkinsabhun...@uncg.edu wrote:
This happens on all text (i.e., not-image) display, to my knowledge.
Obvious examples
5 matches
Mail list logo
