Using Adobe® Flex® 4 - Adobe Blogs

FileSystemComboBox
FileSystemHistoryButton
FormHeading
FormItem
FormHeading
FormItem
HSlider (the labels follow the same rules as the Halo Label control)
LinkBar
LinkButton
Menu
MenuBar
Panel
PopUpButton
PopUpMenuButton
PrintDataGrid
ProgressBar
RadioButton
TabBar
TabNavigator
TitleWindow
ToggleButtonBar
ToolTip
USING FLEX 4
Fonts
VSlider (the labels follow the same rules as the Halo Label control)
Other Halo controls have some limitations when it comes to using the UITLFTextField and TLFTextInput classes. In
some cases, you should use the Spark equivalents. In other cases, you can use the UITLFTextField and TLFTextInput
subcomponents with the Halo control, as long as you avoid using advanced text features, such as editability or the
htmlText property. The following table describes these limitations:
Halo control Description
List-based components (such as
List, FileSystemList, HorizontalList,
TileList, DataGrid, and Tree)
Some list-based components have Spark equivalents (including List,
HorizontalList, and TileList). You can use the UITLFTextField and TLFTextInput
classes in the other components if you do not use selection, editability, HTML
links, or scrolling. Otherwise, you should embed a non-CFF version of the font to
support these controls.
Label and Text Use Spark equivalents such as Label, RichText, and RichEditableText. You can
use UITLFTextField with the Label and Text controls if the text is not selectable
or you do not use the htmlText property to specify the content of the controls.
Otherwise, you should embed a non-CFF version of the font to support these
controls.
TextInput and TextArea Use the Spark equivalents. Otherwise, you should embed a non-CFF version of
the font to support these controls.
29