Indeed, changing ftdiff.c like such:
--- a/ft2demos/src/ftdiff.c 2007-04-02 13:44:11.000000000 +0000
+++ b/ft2demos/src/ftdiff.c 2007-04-02 19:21:58.000000000 +0000
@@ -259,7 +259,7 @@
if ( state->need_rescale && state->size )
{
FT_Set_Char_Size( state->face, 0, state->char_size * 64,
- 0, state->resolution );
+ state->resolution, state->resolution );
state->need_rescale = 0;
}
}
does make it work correctly.
But I'm still not certain that it isn't better to instead change
FT_Set_Char_Size() in freetype2/src/base/ftobjs.c to do the same
thing to horz_resolution and vert_resolution that it now does to
char_width and char_height. (And which is why the first 0 above
in the call to FT_Set_Char_Size() does not have to be changed.)
The significant corruption in the initial display, which would be
fixed by changing the point size with UP or DOWN does not show up
after applying the above patch. There is probably still a bug in
ftdiff.c or in the library, but I don't see it and fixing the res
bug hides it.
-JimC
--
James Cloos <[EMAIL PROTECTED]> OpenPGP: 1024D/ED7DAEA6
_______________________________________________
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel
