Re: glyphWithName: broken on Tiger ?
Re: glyphWithName: broken on Tiger ?
- Subject: Re: glyphWithName: broken on Tiger ?
- From: Robert Clair <email@hidden>
- Date: Wed, 1 Jun 2005 18:22:20 -0400
It sounds to me like you were relying on something that the documentation clearly stated was not a guarantee, and now you're being bitten by it and you want to blame someone else.
Sorry, but that's your bug.
Absolutely wrong. If the docs say that glyph names can be arbitrary, expect the unexpected.
Please read the docs again.
"Glyph names in fonts do not always accurately identify the glyph"
The way I learned English what the doc is doing is warning me that the glyph naming of some fonts is flakey, *not* that the routine is flakey or deprecated or unsupported. Are you suggesting that for a given font the glyph names are a function of the weather ?
I would absolutely expect to get a -1 or an unexpected glyph for an arbitrary font. What I do not expect is for it to suddenly stop working on the *same* font merely because I upgraded.
It doesn't return -1 or the wrong glyph. It now uniformly returns 0, the null glyph, for every font for which it used to work - i.e. "broken".
....Bob
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden