It must be something that the host is doing that’s mucking around with the graphics system - maybe there’s some kind of scaling setting? Can’t think of anything it could be though, I’m a bit stumped by that!
If that is the case, then chkn you should try the last commit of April (9c21813960fb) which is one commit prior to when the font styles stuff was integrated for the first time. You should probably try the commit after that too.
However, by the look of your second screenshot, I’m not so sure that is the problem. The OSXTypeface looks right, it has a proper font name and font style, so the conversion from default font names to actual font names worked fine.
What version of OS X are you using?
Have you tried the plugin in other mac hosts? Do you see the same issue?
Are you specifying an actual typeface name for the font? It might just be that you need to make sure that name is still correct now. E.g. you can’t ask for “Arial Regular” any more, because the “Regular” bit is now specified separately in the style name.
That is very odd. Jules original theory may be correct. Logic Pro may be messing with the graphics context some how. You should try compiling the demo plugin with the CoreGraphics Renderer off to test this. This will tell you if it is a CoreGraphics issue.
I don’t own a copy of Logic Pro so there isn’t any way I can debug the problem. It would be interesting to know if this occurs with Logic Pro and OS X 10.7.
The only thing I can suggest is to step through the changes made to juce_mac_Fonts.mm since the beginning of may to try to isolate the actual lines that cause this issue:
update - lasted change does not help (obviously it wasn’t designed to remove this issue)
[quote]The only thing I can suggest is to step through the changes made to juce_mac_Fonts.mm since the beginning of may to try to isolate the actual lines that cause this issue: https://github.com/julianstorer/JUCE/co … c_Fonts.mm[/quote]
It was the inital commit from the first of may which caused the problems - nobody else with Logic who can confirm this issue?
I think I’ve seen this though this wasn’t on my development system (still using 2.0.18) , so I can’t reproduce it atm.
This was with XCode 3.2.6, Logic (I assume 9) and a Juce tip from last week.