1 person found this helpful
Thanks for the suggestion, if I use s|global the fonts are then being used BUT only if I have the Spark Theme active. Still not being used if I have the "Halo" theme active
Mx components require embedAsCFF: false
Nope, CFF embedded fonts (embed-as-cff / embedAsCff) can definitely be used by MX controls as evidenced by the following threads.
http://opensource.adobe.com/wiki/display/flexsdk/FTE+and+TLF+text+in+MX+components (out of date but still applicable)
There was another excellent Adobe help example by Peter deHaan for AdvancedDataGrid but I can't re-locate it
Basically set the "Use Flash Text Engine in MX components" compiler option or directly set the textFieldClass to UIFTETextField or UIFTETextInput (there are a couple of others) dependant on control type, but the compiler option does this all for you.
I have even seen it working myself as I can see my fonts coming through, when I apply the font-family DIRECTLY to a control type, ie mx|Label it just doesn't work when I apply any styling to the global CSS definition using the Halo theme.
How would I get direct Adobe support for this? It is becoming a major problem for us now....
Sorry, didn't see that you were using the FTE in MX option.
You can contact support this way: http://www.adobe.com/support/contact/
What happens if you use the Spark theme instead of the Halo theme. Maybe
the halo theme's defaults are trumping yours.
I had the same issue, I was using embed-as-cff: false, and the font was not showing up. I changed it to embedAsCFF: false; and hey presto, the embedded fonts appeared in the mx components I had assigned them to. Seems like a bug to me, you should be able to use either variation in my opinion.
I just ran into a similar issue.
you should be able to use either variation in my opinion.
Agreed, Adobe should get this idea of deprecating Halo (especially while Spark isn't even complete!) out of their minds and support both component sets as equals--different component set strategies for different types of applications. Halo should be the "ready to go production out of the box (with a bit of CSS)" component set, for enterprise and other devs who don't care about heavy UI customization. Spark should be the highly-customizable designer-focused component set that starts off with it's current plain look "out of the box".
Protest anti-Halo bigotry. Halo deserves equal attention in Design View, QA testing and Flash Builder bugfixes!