[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
freetype2 beta 8 - two issues.
From: |
Toby J Sargeant |
Subject: |
freetype2 beta 8 - two issues. |
Date: |
Tue, 19 Sep 2000 02:43:03 +1100 |
User-agent: |
Mutt/1.1.9i |
In developing a python wrapper for freetype 2, I have come across the
following issues:
1) rendering a space glyph using ft_render_mode_mono fails inside the raster1
module because the glyph has no contours. Is this correct behaviour?
If it is, would it be possible to return a more meaningful error than
this?
bash-2.03$ python ftstring.py
Traceback (innermost last):
File "ftstring.py", line 137, in ?
antialias=0)
File "ftstring.py", line 112, in renderGlyphs
ft_glyph.toBitmap(ft2_interface.ft_render_mode_mono)
ft2_interface.error: (1, "can't open stream")
2) the fact that ft_render_direct is not supported by raster1 causes
FT_Outline_Render to fail, because ft_black_render returns
Raster_Err_Unsupported which causes FT_Outline_Render to quit
without trying the smooth rasterizer. I've used gdb to jump execution
past the quit, and the smooth rasterizer handles it just fine.
Thanks,
Toby.
- freetype2 beta 8 - two issues.,
Toby J Sargeant <=