Label TTF support not working « cocos2d for iPhone

cocos2d for iPhone » Programming » cocos2d support (graphics engine)

Label TTF support not working

(18 posts) (7 voices)

Started 2 years ago by bdittmer
Latest reply from Nate

Tags:

bdittmer
Member

Hello all, I am experimenting with the latest .8.2-beta and I am unable to get the TTF support to work properly. Using one of the project templates, including a ttf font, and simply modifying the "Hello World" label causes the application to crash with the follow stack trace:

2 CoreFoundation 0x302d6ffb -[NSObject doesNotRecognizeSelector:] + 187
3 CoreFoundation 0x3026e056 ___forwarding___ + 902
4 CoreFoundation 0x3024a0a2 _CF_forwarding_prep_0 + 50
5 FontTest 0x0001dba7 -[Texture2D(Text) initWithString:fontName:fontSize:] + 119

I have isolated it down to line 337 of Texture2D.m:

dim = [string sizeWithZFont:zFont];

It appears that the category method FontLabel adds (sizeWithZFont) is not being recognized. Has anyone else experienced this problem? I ran into it originally by upgrading an .8.1 app to .8.2-beta and thought it might be a problem with my migration, however it still happens in the .8.2-beta project template. Any assistance with this is appreciated.

Brian Dittmer
http://www.sadrobotsoftware.com

Posted 2 years ago #
bdittmer
Member

I figured out how to make this work and there is an issue with the template. You will need to setup a new build target for the FontLabel and add all of the FontLabel sources to it. A standard static library build target works fine. Once this is created drag and drop it to the top of the cocos2d libraries build target. It will build FontLabel first and then the cocos2d build will use that library. I will open a bug for this.

Posted 2 years ago #
riq
Key Master

yes, could you open an issue ? thanks.

Posted 2 years ago #
Houly
Member

I've got another Problem with this. My App doesn't crash if I use a custom ttf, or better say, it doesn't crash if i type some non excisting font into fontName.

First I thougth it was me, then I openend the new Template with the hell world example. Just changed the Name from "Marker Felt" to "Anything I want". Nothing happens. I imported some of the fonts you distribute with the beta build. Same thing here, nothing happens.

I tried the above method with the target thing, but that changed nothing.

Do I get something wrong here?

Posted 2 years ago #
riq
Key Master

It's probably the same bug (?).
but, just in case, could you try the "FontTest" test that comes with v0.8.2 beta ? Thanks.

Posted 2 years ago #
Houly
Member

The FontTest works fine.

So it must be the same thing with the template.

Posted 2 years ago #
riq
Key Master
this is the fix:

Add these options to "Other Linker Flags" in the target build settings:
```
-ObjC
-all_load
```
Posted 2 years ago #
ob1
Member

What does -ObjC do exactly ? I think it causes problems if you have Admob and other parts using JSON.

Posted 2 years ago #
riq
Key Master

I thought that -ObjC loaded all objective-c extensions, but since SDK 3.0 it's not enough to do that. You need to add the -all_load too.

Well, I might be wrong. Perhaps -all_load is enough, but I'm not sure.

Posted 2 years ago #
AkumaStreak
Member

Can someone explain (brief summary of the diff. label classes) what we had before the external FontLabel lib came along? I was thinking cocos2d had some ttf support before, no? I notice in the release notes for 8.2 it says something like support for any/arbitrary ttf fonts... what did we have before? Only fonts support by UILabel or something? I am just now starting to need dynamic text in my apps and want to take the best approach. Was all text before generated from bitmap font files or something?

Thanks,
Jason

Posted 2 years ago #
AkumaStreak
Member

Ok , I looked over the classes, and I think I understand them now. Am I correct when saying that this new ttf font support is for the Label class, and that it will subsequently be slow for things like in game score text vs. using Hiero/BitmapFontAtlas? However FontLabel stuff is supremely awesome for static text needs in most cases?

Thanks,
Jason

Posted 2 years ago #
AkumaStreak
Member

Here are some links concerning why the linker flag is needed: http://www.cocoabuilder.com/archive/message/xcode/2008/7/27/23699
http://developer.apple.com/mac/library/qa/qa2006/qa1490.html

Looks like using only the -ObjC flag is the best option, if it works.

Posted 2 years ago #
AkumaStreak
Member

No matter whether I put these linker flags global to my project, or just for FontLabel, I get these errors:

/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/libtool: -dynamic not specified, -all_load invalid
/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/libtool: -dynamic not specified the following flags are invalid: -ObjC

Bah!

I tried adding dynamic, wouldn't fly either. Anyone have more info?

Posted 2 years ago #
AkumaStreak
Member

Ok, sorry for the confusion. At a minimum all_load is needed (for this stuff to work), but I am using both flags (-ObjC -all_load). From what I read, -ObjC should be the only one needed, but there is some issue requiring the other for now (maybe later the -ObjC will suffice).

One of my probs was that I wasn't linking libz (oops).

The other problem was that the Computer.ttf font I downloaded wouldn't work (I could not open a CGDataProviderRef via CGDataProviderRef fontDataProvider = CGDataProviderCreateWithFilename([fontPath fileSystemRepresentation]) in FontManager.m for this ttf for some reason). Are there issues with some ttfs making them unusable?

Thanks,
Jason

Posted 2 years ago #
AkumaStreak
Member

Nevermind, I re-downloaded the computer font I was asking about, and it appears to work. :-/

Posted 2 years ago #
dandushka
Member

hey guys,

I can get custom fonts to work with -all_load / -ObjC. However, if I now want to add the cocoslive library, these linker flags cause the following bunch of errors:

"_ov_read", referenced from:
-[PASoundSource initBuffer] in libcocos Live.a(PASoundSource.o)
"_ov_clear", referenced from:
-[PASoundSource initBuffer] in libcocos Live.a(PASoundSource.o)
"_ov_info", referenced from:
-[PASoundSource initBuffer] in libcocos Live.a(PASoundSource.o)
"_ov_open", referenced from:
-[PASoundSource initBuffer] in libcocos Live.a(PASoundSource.o)

Any ideas?

Thank you kindly,

d

Posted 2 years ago #
dandushka
Member

all right. I guess I needed the vorbis library and also had to remove the -all_load. Now it's working fine. cheers.

Posted 2 years ago #
Nate
Member

@dandushka I noticed that the static library for cocosLive included PASoundEngine files in the Compile Sources. When I removed those files from the Compile Sources in cocoesLive Build Phases I was able to use the cocosLive static library.

Posted 10 months ago #

RSS feed for this topic

Reply

You must log in to post.