Hi I tried to migrate from 5.0.1 to 5.0.5 but someting strange happened to all the texts...
{"name":"fonts.PNG","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/4\/f\/4f443151664dbff0c3979634c779182a.png","w":492,"h":65,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/4\/f\/4f443151664dbff0c3979634c779182a"}
//The 5.0.5 and 5.0.1 labels are not drawn by the program i just labeled the image...
In the left part, the version label seems to be kind of too shrunk whereas the right side seems to be a bit scaled in 5.0.5. I read the changes from 5.0.1 to 5.0.5 but haven't found one, that would correspond to this problem. What have I possibly done wrong?
Thanks.
Are you sure it's the same version of FreeType? There could be differences there.
Otherwise please provide a short test program with the associated font file.
Well I downloaded Windows binaries so I didn't have to care about freetype at all... Anyway I will make a short demo and post it here.
//edit: So here is the code:
And here are the results:
5.0.1
501.png
5.0.5
505.png
//edit: So I suppose that the problem is caused by the fact, that provided Windows binaries have been built with different version of freetype, right? That's unfortunate I'd say, because the 5.0.5 version seems a bit defective.
I tested on Linux with 5.01 and 5.0.5. The results are bit-identical. So it's probably a difference in how the Windows binaries were made. Michał might know.
PS. Next time, provide the whole source. Don't make it hard for testers.
You mean "whole" as with includes as well? All right...
I'm syncing from time to time dependencies. Yes, I did updated FreeType to newer version. I can update again and artifact may just dissapear.
I will try.
Thank's a lot...
I found a reason. From version ~2.4.5 FreeType auto hinter is enabled by default, that affect rendering of some fonts. Exactly your case.
In order to fix that FT_LOAD_NO_AUTOHINT should be specified while rendering glyph. That mean some flag should be added to TTF addon, which inform FT that we want or do not want auto hinter.
One way or another that will require new binaries unless you're linking Allegro statically. In that very case you may just use FreeType from 5.0.1 package and you will get properly hinted font.
Edit:
Appropriate changes was committed to Allegro 5.1 branch and should be merged down to 5.0.6 version.
If you want I may prepare a build for you, just tell me what toolchain are you using.
Michal, is you're preparing a binary, could you include the D3D multisampling fix I committed today? The OP asked me when a new release would be coming for that fix. Only if you're already going to be building binaries, might as well kill two birds...
That would be so perfect, that I don't even dare to hope for it... :-D
Don't forget to mention your toolchain .
Well... I had to google the term up.
I hope that I get it correctly... So I use Visual Studio 2010 for everything and I link Allegro binaries (the ones from Michał) dynamically (because I was not able to build it statically even after reading a lot of threads here concerning the topic).
Trent, on what branch yours changes are?
My changes are still only in the 5.1 branch. Revision 15286.
I'll commit the 5.0.6 backported changes later today or tomorrow, after some testing in Windows.
I will do a build when 5.0.6 will be ready.
Peter is already merging changes to 5.0.6 branch.
Thanks...
I like when things get fixed :-)
So how's it going?
Build is ready: http://www.allegro.cc/forums/thread/609685/949007#target
To solve your issue, use FT_LOAD_NO_AUTOHINT flag to load font.
Thank's a lot... I'll try tomorrow.
//edit: I suppose you meant ALLEGRO_TTF_NO_AUTOHINT, but i figured out that much... :-) Works perfectly. Thank's very much.
Yes, my mistake.