Button control padding properties

The values of the paddingLeft, paddingRight, paddingTop, and paddingBottom styles are ignored by Button controls.

The values of the paddingLeft, paddingRight, paddingTop, and paddingBottom styles are honored. To make your icon Buttons look like the SDK 2.0.1 buttons, set the paddingLeft and paddingRight style properties to 0.

RadioButton control height

RadioButton controls do not use the padding properties when determining their height.

The default height of a RadioButton control is 18 pixels.

RadioButton controls take padding properties into account when determining their height.

The default height of a RadioButton control is 22 pixels.

DateChooser year navigator skins

The measuredHeight property was larger because of the changes in Button sizing.

The measuredHeight property was smaller.

DataGrid header skins

To customize the DataGrid header background, you subclass DataGrid and override the drawHeaderBackground() method.

The logic from the drawHeaderBackground() method is in the DataGridHeaderBackgroundSkin class. Also, you use the headerBackgroundSkin style to style DataGrid header background skins.

Menu control's horizontalGap property

The default value of the horizontalGap property for Menu controls is 0. If a Menu has a RadioButton control and an icon, the two overlap.

The default value of the horizontalGap property is 6. Additional space is added for a RadioButton or CheckBox, but not for icons in a MenuItem control.

ScrollBar layout

The width of a ScrollBar was determined by the up arrow skin's width.

The width of a ScrollBar component is the largest width among the up arrow, down arrow, track, and thumb skins.

Disabled ScrollBars

There is no separate skin for the buttons on a disabled ScrollBar.

ScrollArrowSkin has a disabled state. The scroll track was changed from a DisplayObject to a Button. The ScrollTrackSkin now supports Button states.

ScrollBar subcomponent alignment

The up arrow, down arrow, track, and thumb are left-aligned.

The up arrow, down arrow, track, and thumb are center-aligned.

ScrollBar thumb width

The thumb width is the width of the ScrollBar.

The thumb width is the same as the thumb's measuredWidth property.

Padding styles with the Canvas container

Padding styles have no effect on the Canvas container.

Canvas respects padding styles.

Constraint-based layout rules for content-sized containers

Width is ignored when left and right styles are set for components in containers where no width is set. In these cases, the preferredWidth property of a component is used. Height is ignored when top and bottom styles are set for components in containers where no height is set. In these cases, the preferredHeight property of a component is used.

In the following example, the Button control is 40 pixels wide:

Width and height are honored for components with constraints set in content-sized containers. In the previous example, the Button control's width is 100 pixels.

FormItem padding

FormItem controls add unnecessary extra padding underneath the controls when there is more than one control.

No extra padding is allocated underneath a FormItem control.

Scale-9 for Panel containers

The Panel container's skin uses the HaloBorder class.

The Panel container's skin uses the PanelSkin class. Some measurement logic was removed from the Panel class and put into the PanelSkin class.

Border style for Panel containers

You can set the borderStyle property to "solid" and set a borderColor and borderThickness property on the Panel container.

Panel does not support any value for the borderStyle property other than "default".

You can use a combination of explicit heights and widths and absolute positioning to replicate most of the SDK 2.0.1 behavior for alternative borderStyle properties.

The PanelSkin class's implementation of alternative borderStyle properties does not lay out the header and control bar in the correct locations; the Panel is not large enough.

TitleWindow title alignment

The TitleWindow control's textHeight property adjusts to the scale factor.

The TitleWindow control's textHeight property ignores the scale factor.

Accordion header padding

The paddingTop and paddingBottom properties of the Accordion headers is set to -1.

The height of the Accordion container's header is different by one to two pixels.

Accordion subcomponent styles

The styles of the Accordion headers are inherited from the Accordion container.

The Accordion header does not inherit its styles from the Accordion control. Instead, the header uses the headerStyleName style, if one is specified.

The following Accordion styles are deprecated: fillAlphas, fillColors, focusRoundedCorners, horizontalGap, selectedFillColors, and verticalGap.

ColorPicker subcomponent styles

The ColorPicker's swatch panel subcomponent inherits its styles from the ColorPicker control.

Styles that affect the swatch panel do not apply if they are set on the ColorPicker. Instead, the swatch panel uses the swatchPanelStyleName style, if one is specified.

The following ColorPicker styles are deprecated: backgroundColor, columnCount, horizontalGap, verticalGap, previewHeight, previewWidth, swatchGridBackgroundColor, swatchGridBorderSize, swatchHeight, swatchHighlightColor, swatchHighlightSize, swatchWidth, textFieldWidth, and textFieldStyleName.

ComboBox subcomponent styles

The List drop-down in a ComboBox control inherits its styles from the ComboBox control.

The List subcomponent does not inherit its styles from the ComboBox control. Instead, the List subcomponent uses the dropdownStyleName style, if one is specified.

DateChooser subcomponent styles

The cornerRadius and fillColors styles are applied to the next and previous month button subcomponents of a DateChooser control.

Setting the cornerRadius and fillColors style properties affects only the DateChooser itself, but not the subcomponent buttons. To style the buttons, you must edit their skin classes or override the style filters list.

The fillColors and fillAlphas styles of the DateChooser control are deprecated.

DateField subcomponent styles

The DateChooser that pops up from clicking on a DateField inherits its styles from the DateField control.

The DateChooser subcomponent of a DateField control does not inherit its styles from the DateField control. Instead, the DateChooser subcomponent uses the dateChooserStyleName style, if one is specified.

The following DateField styles are deprecated: cornerRadius, fillAlphas, fillColors, headerColors, headerStyleName, highlightAlphas, todayStyleName, and weekDayStyleName.

LinkBar subcomponent styles

The LinkButton subcomponents in a LinkBar control inherit their styles from the LinkBar control.

The LinkButton subcomponents of a LinkBar do not inherit their styles from the LinkBar control. Instead, the LinkButton subcomponents use the linkButtonStyleName style, if one is specified.

MenuBar subcomponent styles

The submenus of a MenuBar control inherit their styles from the MenuBar control.

The submenus of a MenuBar control do not inherit their styles from the MenuBar control. Instead, they use the menuStyleName style, if one is specified.

The backgroundAlpha and backgroundColor MenuBar styles are deprecated.

NumericStepper subcomponent styles

The up and down buttons in a NumericStepper control inherit their border styles from the NumericStepper control.

The up and down buttons of a NumericStepper control do not inherit their border styles from the NumericStepper control.

To change the border styles for a NumericStepper control's button subcomponents, you must subclass the NumericStepper class and override the getters for the downArrowStyleFilters and upArrowStyleFilters properties. For more information, see Subcomponent styles in the Adobe Flex 3 Developer Guide.

TabBar subcomponent styles

The firstButtonStyleName and lastButtonStyleName are inherited from the ButtonBar control on a TabBar control.

The firstTabStyleName and lastTabStyleName styles apply to tab styles.

PopUpManager subcomponent styles

PopUp controls inherit their styles from the Application if they were not explicitly set on the PopUp control.

PopUp controls inherit styles from their owners.

ColorPicker alpha

The ColorPicker control's alpha property is lower, resulting in a lighter control.

The ColorPicker control's alpha property is higher, resulting in a darker control.

Form and FormItem layout

FormItem layout percentage height is not calculated correctly.

FormItem layout code uses BoxLayout. Percentage heights and widths are calculated correctly.

Also, Form and FormItem now support the includeInLayout property.

Percent width rounding rule

If two the width of a container is 275 pixels and two children have the width set to 50%, each component is 137 pixels. The extra pixel is ignored.

If the width of a container is 275 pixels and two children have a width set to 50%, the components widths are 137 pixels and 138 pixels. The extra pixel is applied to one of the components.

Run-time localization

The _CompiledResourceBundleInfo class is not autogenerated for SWC and SWF files.

The _CompiledResourceBundleInfo class is autogenerated for SWC and SWF files.

Parsing rules for .properties files

Parsing .properties files requires removing certain sequences of characters. To use a double quote, you use \\". To use a new-line character, you use \\n. To use a backslash, you use \\\\.

Parsing .properties files use the same rules as Java.

For more information about how properties files are parsed in SDK 3, see Properties file syntax in the Adobe Flex 3 Developer Guide.

Metadata

The keep-as3-metadata compiler option is set in flex-config.xml. The default metadata preserved by the Flex framework includes Bindable, Managed, ChangeEvent, NonCommittingChangeEvent, and Transient.

If you use a third-party library with custom metadata in your projects, you must add that metadata to the keep-as3-metadata option.

SWC libraries define what metadata the linker preserves when linking in code from that library.

When you compile a library, the keep-as3-metadata option instructs the compc compiler what metadata to declare. The option adds the metadata names to preserve in the SWC file's catalog.xml file.

If you use that library, you do not need to specify the metadata when compiling your application.

Profiler

Applications are not compatible with the profiler.

Applications are compatible with the profiler.

Signed framework Runtime Shared Libraries (RSLs)

Applications are not compatible with signed framework RSLs.

Applications are compatible with signed framework RSLs.

Icons for disabled components

When the disabledIcon property is set to null, the icon is invisible when the component is disabled.

The icon for a disabled component does not disappear when the disabledIcon property is set to null. To mimic the Flex 2.0.1 behavior, you can create a style that specifies null for the classes in the appropriate icon properties. For example:

You can set remaining icon properties, such as downIcon and overIcon, to the appropriate skin class; for example, mx.skins.halo.RadioButton.

n/a

n/a

n/a

n/a

n/a

n/a