Searched refs:FT_LOAD_RENDER (Results 1 – 12 of 12) sorted by relevance
144 (FT_Int)family->attrs.load_flags | FT_LOAD_RENDER ); in ftc_basic_family_load_bitmap()
3150 #define FT_LOAD_RENDER ( 1L << 2 ) macro
349 load_flags &= ~FT_LOAD_RENDER; in af_loader_load_glyph()
750 flags &= ~FT_LOAD_RENDER; // don't scan convert (we just want the outline) in generateFacePath()
1349 flags &= ~FT_LOAD_RENDER; // don't scan convert (we just want the outline) in generatePath()
803 load_flags &= ~FT_LOAD_RENDER; in FT_Load_Glyph()807 load_flags &= ~FT_LOAD_RENDER; in FT_Load_Glyph()1020 if ( load_flags & FT_LOAD_RENDER ) in FT_Load_Glyph()4549 load_flags |= FT_LOAD_RENDER; in FT_Render_Glyph_Internal()
1041 * src/base/ftobjs.c (FT_Load_Glyph): Unset FT_LOAD_RENDER if
5341 load_flags &= ~FT_LOAD_RENDER;
4067 is fixed now by clearing the FT_LOAD_RENDER bit of `load_flags'.
2787 - Fonts loaded with FT_LOAD_RENDER no longer cause strange4314 - When using the new bit flag FT_LOAD_RENDER, the FT_Load_Glyph