1 person found this helpful
Spark components use a different font rendering engine than MX components.
You can convert almost all MX components to use the Spark engine via the
Thanks for the quick reply. I was able to make fonts display correctly after hacking the display of some components (mx.controls.FormItem for example) however I did notice a whole buch of runtime warnings that showed up as a result of the workaround such as:
warning: incompatible embedded font 'arialCFFFont' specified for mx.core::UITextFormat. This component requires that the embedded font be declared with embedAsCFF=false.
TextFieldAutomationHelper:captureSelection() - 'selectionBeginIndex' is not implemented in FTETextField.
And in some cases for components I do not even use:
warning: incompatible embedded font 'arialCFFFont' specified for mx.controls::TextInput (TextInput1967) . This component requires that the embedded font be declared with embedAsCFF=false.
Any ideas on how to avoid this noise or do we have to live with this?
I would use the MXFTEText.css file so that the mx controls use the new fonts