A user reported seeing this in the console output of an app built with wxPython 2.9.4.1/wx-osx_cocoa:
2013-10-24 12:00:15.079 Python[784:d07] CoreText performance note: Client called CTFontCreateWithName() using name “.Lucida Grande UI” and got font with PostScript name “.LucidaGrandeUI”. For best performance, only use PostScript names when calling this API.
Furthermore: “it just keeps on coming with every click on the GUI, overwhelming the terminal.”
This looks like something really-low level; is it a wxWidgets problem? Or freetype? Has anyone else seen this?
thanks,
Nat
Nat Echols <nathaniel.echols@gmail.com> writes:
This looks like something really-low level; is it a wxWidgets problem? Or
freetype? Has anyone else seen this?
It is probably wxwidgets related since it does affect wxPerl also.
best
···
--
erik colson
I am having this problem, with wxpython, as well.
Is there any progress? Can I help debug? How? 
Thanks,
Martin
···
On Friday, October 25, 2013 4:42:40 PM UTC+10:30, Erik Colson wrote:
Nat Echols nathanie...@gmail.com writes:
This looks like something really-low level; is it a wxWidgets problem? Or
freetype? Has anyone else seen this?
It is probably wxwidgets related since it does affect wxPerl also.
best
–
erik colson
I tried digging in the code to figure out what was breaking, but my very
crude attempt at a fix didn't work. There turned out to be so many other
things broken on Mavericks that the font problem ended up being a lower
priority; between windows not behaving normally and Python processes
crashing, it has been a complete disaster for us. I don't think any of
these problems are related to the fonts error.
-Nat
···
On Sat, Nov 9, 2013 at 7:37 PM, GreenAsJade <martin.jg.gregory@gmail.com>wrote:
I am having this problem, with wxpython, as well.
Is there any progress? Can I help debug? How?
I tried digging in the code to figure out what was breaking, but my very crude attempt at a fix didn’t work. There turned out to be so many other things broken on Mavericks that the font problem ended up being a lower priority; between windows not behaving normally and Python processes crashing, it has been a complete disaster for us. I don’t think any of these problems are related to the fonts error.
Thanks for responding, though that is rather discouraging!
FWIW, I had a nightmare trying to set up virtualenv with wxpython after the Mavericks install blew away the system python that I had been using. I never solved
that. Once I gave up, the rest of my app seems to work OK all except for this font issue, which fills my users’ system logs…
I’m curious why there appears to be so little noise about this font issue on the net. Is wxpython not used much by Mac developers?
Martin.
···
On Tuesday, November 12, 2013 3:11:56 AM UTC+10:30, Nat Echols wrote:
Ooops, I see it’s probably because there are bigger fish being fried! 
···
On Tuesday, November 12, 2013 9:22:58 PM UTC+10:30, GreenAsJade wrote:
I’m curious why there appears to be so little noise about this font issue on the net. Is wxpython not used much by Mac developers?
FWIW, this message is coming from wxWidgets font.cpp line 271, where CTFontCreateWithName() is called with Lucida Grande as a hardcoded font name during the construction of a thing called a wxFontRefData.
The choice that results in Lucida Grande being called is based on the “m_family” member of this wxFontRefDSata being wxSWISS.
I haven’t yet been able to work out why my m_family is wxSWISS … if I could change that then at least a different font would be named.
Sigh…
For what it's worth, I tried recompiling with the space removed, and the
errors didn't go away. (But it's possible that I did something wrong; I'll
double-check today.)
-Nat
···
On Tue, Nov 19, 2013 at 3:32 AM, GreenAsJade <martin.jg.gregory@gmail.com>wrote:
FWIW, this message is coming from wxWidgets font.cpp line 271, where
CTFontCreateWithName() is called with Lucida Grande as a hardcoded font
name during the construction of a thing called a wxFontRefData.
Whoa, what did you recompile? What space did you remove? Sounds promising … (but does this mean rebuilding all of wxwidgets and wxpython … sounds daunting!)
···
On Wednesday, November 20, 2013 3:10:51 AM UTC+10:30, Nat Echols wrote:
On Tue, Nov 19, 2013 at 3:32 AM, GreenAsJade martin.j...@gmail.com wrote:
FWIW, this message is coming from wxWidgets font.cpp line 271, where CTFontCreateWithName() is called with Lucida Grande as a hardcoded font name during the construction of a thing called a wxFontRefData.
For what it’s worth, I tried recompiling with the space removed, and the errors didn’t go away. (But it’s possible that I did something wrong; I’ll double-check today.)
-Nat
(I don’t think the space between the words Lucida and Grande is likely to be an issue: I think that the calls in between wxSWISS and CTFontCreateWithName do some font name mapping that deals with that … but I’m keen to experiment with trying completely different fonts to make the error go away!)
···
On Wednesday, November 20, 2013 7:44:48 AM UTC+10:30, GreenAsJade wrote:
On Wednesday, November 20, 2013 3:10:51 AM UTC+10:30, Nat Echols wrote:
On Tue, Nov 19, 2013 at 3:32 AM, GreenAsJade martin.j...@gmail.com wrote:
FWIW, this message is coming from wxWidgets font.cpp line 271, where CTFontCreateWithName() is called with Lucida Grande as a hardcoded font name during the construction of a thing called a wxFontRefData.
For what it’s worth, I tried recompiling with the space removed, and the errors didn’t go away. (But it’s possible that I did something wrong; I’ll double-check today.)
-Nat
Whoa, what did you recompile? What space did you remove? Sounds promising … (but does this mean rebuilding all of wxwidgets and wxpython … sounds daunting!)