Flex 4 SDK Release Notes

This document contains release notes and installation instructions for Adobe® Flex® 4 SDK.

About Flex 4 SDK
What’s new
Installation instructions
Compatibility issues
Using Datavisualization with the Flex SDK 4
Using Automated Testing with the Flex SDK 4
Known issues
Flex 4 Documentation
About Flex 4 SDK
Flex 4 SDK includes the Flex framework (also known as the Flex class library), Flex command-line compilers, the Flex debugger, the ASDoc utility, and the debugger version of Flash Player and AIR runtimes. Use the Flex 4 SDK to develop, compile, and deploy Flex applications that connect to XML and SOAP web services or connect to various server technologies such as PHP, ColdFusion, Java, and .NET using a server technology such as BlazeDS. Flex applications can be built and configured to target browsers via the Flash Player runtime or desktops via the AIR runtime.

What’s New in Flex 4
This section lists some of the major new features and changes for Flex 4 SDK. See the What’s New in Flex 4 article for more information on new features.

A new and powerful component skinning architecture, known as “Spark”. To learn more about the Spark skinning architecture, see the Introducing Skinning in Flex 4 article.
A set of components that use the Spark architecture that can be mixed and matched with the MX components that are available in Flex 3. To learn more about the Spark architecture and components, see the Brief Overview of the Spark Architecture & Component Set article.
Support for declarative, dynamic MXML graphics, as well as for static, optimized FXG graphics.
A new default look (the “Spark” theme) for MX and Spark components which support a new set of styles.
More powerful layout capabilities, including support for MXML graphic elements, improved support for rotation and other transforms, support for assignable custom layouts, and enhanced z-order management capability. To learn more about layouts in Flex 4, see the Spark Layouts with Flex 4 article.
Numerous new and/or improved effects, including support for animating MXML graphic elements, support for animating arbitrary types via custom interpolators, a more flexible easing API, and more automatic behaviors. To learn more about effects in Flex 4, see the Effects in Adobe Flex pair of articles.
3D effect support.
Animation of Flash filters, including Pixel Bender shaders.
More advanced text support, based on the Flash Text Engine and the Text Layout Framework, as well as support for CFF (Compact Font Format) fonts.
Improved compiler performance.
New MXML language features, including the MXML 2009 namespace, much improved support for States, and the Declarations, Library, and Definition tags.
CSS enhancements, including support for namespaces, descendant selectors, ID selectors, multiple class selectors, and pseudo-selectors for component states.
Convenient syntax for two-way databinding.
ASDoc improvements including support for Linux platforms, comments defined in mxml files, and creation of DITA XML files that allow for documentation to be displayed as tooltips within FlashBuilder.
Improved HTML templates, based on SWFObject.
Hosting of SDK runtime shared libraries (RSLs) at adobe.com.
Additional locale support for developing localized applications.
Support for JAWS 11 – As of version 4, Flex supports the JAWS 11 screen reader.
Installation instructions
The Flex SDK installation is delivered as a ZIP file and contains the Flex framework, Adobe AIR framework, and command-line tools, such as the mxmlc command-line utility, Adobe AIR command-line utility, the ASDoc utility, the Flex command-line debugger, and the debugger version of Flash Player.

Uninstall Current Flash Player

You should use Flex SDK with the latest version of the debug Flash Player 10. Prior to installing the Flex SDK, you should uninstall your current Flash Player.

Windows-Plugin-based browsers
Run the appropriate uninstaller available from this Tech Note.

Macintosh
Run the appropriate uninstaller available from this Tech Note.

Linux
Manual removal (for users who installed the plug-in via Install script):

Delete the libflashplayer.so binary and the flashplayer.xpt file in directory /home//.mozilla/plugins/

RPM removal:

As root, enter the following command:

# rpm -e flash-plugin
Click Enter and follow the prompts.
Install the Flex SDK

1. Download Flex SDK ZIP file from the Adobe website or the Adobe Open Source site.

Create a directory to contain Flex SDK

Extract the Flex SDK ZIP file to this directory. The Flex SDK contains the following directories:

/ant — Contains Flex Ant Tasks.
/asdoc — Contains helper files for the ASDoc tool that creates HTML documentation from your MXML and ActionScript source code.
/bin — Contains the mxmlc, compc, asdoc, and fdb utilities. The bin directory also contains the jvm.config file, which specifies Java settings that you can modify, if necessary.
/frameworks — Contains compiled framework classes, configuration files, and framework source code.
/lib — Contains JAR files used by the utilities.
/runtimes — Contains installers for the Adobe AIR runtime inside the air directory and installers for debug versions of Flash Player 9 inside the player directory.
/samples — Contains sample applications.
/templates — Contains HTML templates for Flash Player detection and browser integration and inside the air folder, a sample Adobe AIR application.xml file.
Ensure that the Java Runtime Environment (JRE) is installed on the computer and that the java_home/bin directory is defined in the system path. JRE 1.5,or 1.6 is required.

Install the appropriate debug Flash Player from the install_root/runtimes/player/platform directory.

(Optional) When the Flash Player installation finishes, restart your computer to ensure that the updated Flash Player browser plug-in is enabled.

Compatibility issues
Backwards compatibility compiler argument – There are a number of Flex SDK backwards compatibility changes in Flex 4. You can return the behavior to Flex 3 by using the compiler argument: -compatibility-version.

To get the full list of issues, please refer to the Flex 4 Backwards Compatibility document. You may also learn more about the differences between Flex 3 and Flex 4 in this article.

Using the Data Visualization components with Flex SDK 4
As of Flex 4, automated testing support is part of the SDK distribution.

Using Automated Testing with Flex SDK 4
As of Flex 4, automated testing support is part of the SDK distribution.

Known issues
This section contains selected known issues. For a complete list of Flex issues and their status, see the public bugbase. The public bugbase lets you search for known issues, comment on them, and add new bugs.

Tip: Use Filters to customize your search.

http://bugs.adobe.com/jira/browse/SDK-17285 – Focus does not work correctly for components that draw off-screen in Internet Explorer. Button, RadioButton, CheckBox, and Sliders draw shadows into the “negative territory.” If these components are placed at (0,0), they won’t correctly be picked up when tabbing to switch the focus.

The workaround is to either move the component so it’s not at (0,0) anymore and doesn’t draw anything off-screen, or to change the component skins and create a custom skins that doesn’t draw shadows starting at (-1, -1).””

http://bugs.adobe.com/jira/browse/SDK-20140 – item renderer selection gets out of sync when transitions are used
http://bugs.adobe.com/jira/browse/SDK-20270 – If some visual elements appear in some states and not in others, you may need to add a transparent Rect to cover the entire hit area to prevent an infinite loop of state changes.
http://bugs.adobe.com/jira/browse/SDK-20880 – Masking a UIComponent is not currently supported
http://bugs.adobe.com/jira/browse/SDK-20944 – spark.components.VideoPlayer – Removing VideoPlayer While Playing Doesn’t Remove Audio
http://bugs.adobe.com/jira/browse/SDK-23050 – backgroundImage is not supported with Spark skins theme
http://bugs.adobe.com/jira/browse/SDK-23154 – Avoid setting backgroundColor on a global style selector. This style gets picked up by several components that may cause unintended behavior to avoid this, set the backgroundColor style on specific components instead of on the global style selector.
http://bugs.adobe.com/jira/browse/SDK-23416 – RTE if TextArea is used in List ItemRenderer. Workaround is to import import flashx.textLayout.elements.TextFlow; and add this to the List typicalItem=”{(TextFlow(data[0]).deepCopy())}”
http://bugs.adobe.com/jira/browse/SDK-23452 – Tooltips cannot display 4-byte characters on Windows.
http://bugs.adobe.com/jira/browse/SDK-23911 – Sorting or dragging/dropping of pending or failed items isn’t supported.
http://bugs.adobe.com/jira/browse/SDK-24055 – When Alert is used in a module but not defined in the main app, current moduleFactory should be passed to Alert.show() so Alert can pick up styles correctly.
http://bugs.adobe.com/jira/browse/SDK-24060 – When module uses Alert but the loading Application does not. A variable of type PopUpManager should be added to the loading Application to avoid Runtime Exception.
http://bugs.adobe.com/jira/browse/SDK-25270 – AddAction/RemoveAction interferes with DisplayObject sharing
http://bugs.adobe.com/jira/browse/SDK-25302 – VideoPlayer unable to load Amazon Cloudfront videos
http://bugs.adobe.com/jira/browse/SDK-25513 – Incremental compiler fails to pick up metadata changes. Work around to do full compile. You can also download a patched .jar from the bug which fixes the problem.
http://bugs.adobe.com/jira/browse/SDK-25618 – In Firefox 3.6, Scroll bars show in browser after first click.

Workaround is to add the following to the style section of the HTML template:

a:focus, object:focus {
outline: none;
-moz-outline-style: none;
}
http://bugs.adobe.com/jira/browse/SDK-25521 – List doesn’t respect its Layout’s typicalLayoutElement
http://bugs.adobe.com/jira/browse/SDK-25412 – Spark List isnt updating renderers correctly when specifying custom itemRendererFunction and using virtual layout. Workaround: Reset the itemRendererFunction to the same function after setting the data provider.
http://bugs.adobe.com/jira/browse/SDK-25419 – List renderer transitions get stuck when allowMultipleSelection is true
http://bugs.adobe.com/jira/browse/SDK-25358 – Elements with a 3D rotation inside a Scroller are affected by the scrollbars of sibling elements
http://bugs.adobe.com/jira/browse/SDK-25480 – Rotate3D can cause elements to not be clickable when they have a non-zero z value
http://bugs.adobe.com/jira/browse/SDK-25231 – Spark MXDataGridItemRenderer leaks content outside of its bounds
http://bugs.adobe.com/jira/browse/SDK-25773 – The ant script to build themes requires a compc.jvm.args parameter. Workaround: Pass in compc.jvm.args:

ant -Dcompc.jvm.args=-Xmx512m
http://bugs.adobe.com/jira/browse/SDK-25781 – Using FTETextfield for an AIR application causes a runtime error when you open a Window with MX components. To get around this issue, you will need to use embedded fonts for this application and add the following to a Style block in your application:

@namespace mxair “mx.core.windowClasses.*”;
mxair|StatusBar
{
textFieldClass: ClassReference(“mx.core.UIFTETextField”);
}

mxair|TitleBar
{
textFieldClass: ClassReference(“mx.core.UIFTETextField”);
}

Flash Builder 4 System requirements

Flash Builder 4 for Windows (Standard and Premium editions)
2GHz or faster processor
Microsoft® Windows® XP with Service Pack 3, Windows Vista® Ultimate or Enterprise (32 or 64 bit running in 32-bit mode), Windows Server® 2008 (32 bit), or Windows 7 (32 or 64 bit running in 32-bit mode)
1GB of RAM (2GB recommended)
1GB of available hard-disk space
Java™ Virtual Machine (32 bit): IBM® JRE 1.5, Sun™ JRE 1.5, IBM JRE 1.6, or Sun JRE 1.6
1024×768 display (1280×800 recommended) with 16-bit video card
DVD-ROM drive
Eclipse 3.4.2 or 3.5 (for plug-in installation)

Flash Builder 4 for Mac OS (Standard and Premium editions)
Intel® processor
Mac OS X v10.5.6-10.6
1GB of RAM (2GB recommended)
1GB of available hard-disk space
Java Virtual Machine (32 bit): JRE 1.5 or 1.6
1024×768 display (1280×800 recommended) with 16-bit video card
DVD-ROM drive
Eclipse 3.4.2 or 3.5 Carbon version (for plug-in installation)

Flash Builder 4 data-centric development features
Adobe® ColdFusion® server: ColdFusion 8.0.1 or 9
J2EE server: BlazeDS 4 or Adobe LiveCycle® Data Services 3
PHP server: PHP 5.2 or Zend Framework 1.9.4 (included with Flash® Builder™ 4)
Web services: WSDL 1.1
Flex 4 SDK
Windows XP Professional with Service Pack 2 or 3, Windows 7 (32 bit), or Windows Vista (32 bit)
Mac OS X v10.5.6-10.6 (Intel only)
Ubuntu 9.10
Fedora Core 12
Language versions
Adobe Flash Builder 4 software is available in the following languages:

Chinese Simplified
English
French
German
Japanese
Russian

Flash Builder 4.0 Release Notes

Welcome to Adobe® Flash® Builder™ 4. This document contains late-breaking product information, updates, and troubleshooting tips not covered in the Flash Builder 4 documentation.

Minimum system requirements

What’s included

Install your software

Uninstall your software

Trial software

Electronic licensing

Registration information

Known issues

Customer care

Other resources

Minimum system requirements

For the latest system requirements, please visit www.adobe.com/go/flashbuilder4_systemreqs

What’s included

DVD:

The Flash Builder 4 DVD includes the following:

Flash Builder 4 Standalone install folder
Flash Builder 4 Eclipse Plug-in install folder
Extras folder that includes: *
LiveCycle Data Services 3.0 installer
Adobe Application Modeling Plug-in for Eclipse 3.4
Adobe Application Modeling Plug-in for Eclipse 3.5
LiveCycle Service Discovery Plug-in for Flash Builder 4.0
Flex 4 Test Automation Plug-in **
Flash Builder 4 Readme
* The contents of the Extras folder is not included in the Electronic Software Distribution (ESD) download.

** Not included in the Electronic Software Distribution (ESD) download, but available as a separate download at www.adobe.com/go/flex_plugin

Install your software

1. Before you install, quit all browsers and close all applications currently running on your system–including other Adobe applications, chat applications and Microsoft Office applications. It is also recommended to temporarily turn off virus protection during the installation process. Uninstall any previously installed versions of Flash Builder 4.

2. You must have administrative privileges or be able to validate as an administrator.

3. Do one of the following:

Install Flash Builder 4 Standalone on Windows:

a. Log in as the Windows Administrator or as a computer administrator (a user account with administrator privileges).

Note: If you attempt to install without administrator privileges, the installation will complete with flagged issues. However, you will have installed an incomplete version of Flash Builder that you will not be able to run.

b. Prior to installing, uninstall any prerelease versions of Flash Builder 4.

c. Insert the DVD in your drive, and follow the on-screen instructions. If the installer does not launch automatically, navigate to the Adobe Flash Builder 4 Standalone folder found at the root level on the DVD and double-click Set-up.exe to start the installation process.

If you downloaded the software from the web, the installer will self-extract after the folder to copy the installer is selected and launch automatically. If the installer does not launch automatically, open the folder, navigate to the Adobe Flash Builder 4 Installer folder, double-click Set-up.exe, and then follow the on-screen instructions.

d. Accept the user license agreement. When prompted, enter your serial number or choose the trial option. Select a language if not selected.

e. If you are installing as an upgrade, the installer will check your system to find the valid upgrade product. If it cannot find it, it will ask you to input the serial number of the product being upgraded. You can also install the software in trial, then input your new and previous serial numbers in the serialization screen shown during launch.

Install Flash Builder 4 Plug-in on Windows:

NOTE: Flash Builder 4 is only supported on Eclipse 3.4 or higher.

CAUTION: Do not install the plug-in version of Flash Builder 4 into a copy of Eclipse that is already hosting Flex Builder 3 plug-in. If you want to continue running Flex Builder 3 plug-in, download a new copy of Eclipse and use that when installing Flash Builder 4 plug-in, or choose bundled Eclipse option in the installer. In addition, be sure to use separate Eclipse workspaces for each installation.

a. Log in as the Windows Administrator or as a computer administrator (a user account with administrator privileges).

Note: If you attempt to install without administrator privileges, the installation will complete with flagged issues. However, you will have installed an incomplete version of Flash Builder that you will not be able to run.

b. Prior to installing, uninstall any prerelease versions of Adobe Flash Builder 4 Eclipse Plug-in.

c. Insert the DVD in your drive, and follow the on-screen instructions. If the installer does not launch automatically, navigate to the Adobe Flash Builder 4 Eclipse Plug-in folder found at the root level on the DVD and double-click InstallFlashBuilder4Plugin.bat to start the installation process.

If you downloaded the software from the web, the installer will self-extract after the folder to copy the installer is selected and launch automatically. If the installer does not launch automatically, open the folder, navigate to the Adobe Flash Builder 4 Plugin Installer folder, double-click InstallFlashBuilder4Plugin.bat, and then follow the on-screen instructions.

d. Accept the license agreement and follow the prompts.

e. If you are installing as an upgrade, the installer will check your system to find the valid upgrade product. If it cannot find it, it will ask you to input the serial number of the product being upgraded. You can also install the software in trial, then input your new and previous serial numbers in the serialization screen shown during launch.

Install Flash Builder 4 Standalone on Mac:

a. Log in as the Administrator or as a computer administrator (a user account with administrator privileges).

b. Prior to installing, uninstall any prerelease versions of Flash Builder 4.

c. Insert the DVD in your drive, and follow the on-screen instructions. If the installer does not launch automatically, navigate to the Adobe Flash Builder 4 Standalone folder found at the root level on the DVD and double-click Install.app to start the installation process.
If you downloaded the software from the web, open the folder, navigate to the application folder, double-click Install.app, and then follow the on-screen instructions.

d. Accept the license agreement and follow the prompts.

e. If you are installing as an upgrade, the installer will check your system to find the valid upgrade product. If it cannot find it, it will ask you to input the serial number of the product being upgraded. You can also install the software in trial, then input your new and previous serial numbers in the serialization screen shown during launch.

Install Flash Builder 4 Plug-in on Mac:

NOTE: Flash Builder 4 is only supported on Eclipse 3.4 or higher.

CAUTION: Do not install the plug-in version of Flash Builder 4 into a copy of Eclipse that is already hosting Flex Builder 3 plug-in. If you want to continue running Flex Builder 3 plug-in, download a new copy of Eclipse and use that when installing Flash Builder 4 plug-in, or choose bundled Eclipse option in the installer. In addition, be sure to use separate Eclipse workspaces for each installation.

a. Log in as the Administrator or as a computer administrator (a user account with administrator privileges).

Note: If you attempt to install without administrator privileges, the installation will complete with flagged issues. However, you will have installed an incomplete version of Flash Builder that you will not be able to run.

b. Prior to installing, uninstall any prerelease versions of Adobe Flash Builder 4 Eclipse Plug-in.

c. Insert the DVD in your drive, and follow the on-screen instructions. If the installer does not launch automatically, navigate to the Adobe Flash Builder 4 Eclipse Plug-in folder found at the root level on the DVD and double-click FB4_Plugin_Mac_Installer app to start the installation process.

If you downloaded the software from the web, open the folder, navigate to the Adobe Flash Builder 4 Plugin Installer folder, double-click FB4_Plugin_Mac_Installer app, and then follow the on-screen instructions.

d. Accept the license agreement and follow the prompts.

e. If you are installing as an upgrade, the installer will check your system to find the valid upgrade product. If it cannot find it, it will ask you to input the serial number of the product being upgraded. You can also install the software in trial, then input your new and previous serial numbers in the serialization screen shown during launch.

NOTE: You must create a new workspace before beginning. Select File > Switch Workspace from the menu bar and enter a new folder name. If the folder doesn’t exist, Eclipse creates it.

4. For detailed installation instructions for Flex 4 Automation Plug-in, go to www.adobe.com/go/flex_plugin

Note: In order to install additional components or reinstall your software after your original installation, you will need access to the original installer (CD, DVD or the download from the web). Repair is not an available option.

Uninstall your software

Before you uninstall, quit all browsers and close all applications currently running on your system–including other Adobe applications, chat applications and Microsoft Office applications.

In Windows XP, open the Windows Control Panel and double-click Add or Remove Programs. Select the product that you want to uninstall, click Change/Remove, and then follow the on-screen instructions.
In Windows Vista and Windows 7, open the Windows Control Panel and double-click Programs and Features. Select the product that you want to uninstall, click Uninstall, and then follow the on-screen instructions.
IMPORTANT: Mac OS has new uninstall functionality. DO NOT drag applications to the trash to uninstall them. To safely uninstall on Mac OS X, double-click on the Uninstall alias located in the Application folder. Select Remove Preferences, then Authenticate as an administrator and follow the on-screen instructions.
Note: If you want to install the product on a different computer, you must first deactivate the software on your computer. To deactivate, choose Help > Deactivate Flash Builder.

Trial software
Entering a serial number

Enter the serial number for the software you purchased in the serialization screen. The serialization screen will load the first time you launch the application (if using the Adobe Flash Builder 4 Eclipse Plugin, it may take more than one launch for the serialization screen to appear).

Only applications running as a trial will recognize the new serial number. If any of the applications have already been serialized with a different serial number, it will continue to use that serial number until you remove the older serial number using the Help > Deactivate Flash Builder. Then on the next launch of the application, it will recognize the new serial number.

Volume licensing

Volume licensing customers cannot purchase from a trial directly. Please contact your reseller or authorized Adobe licensing center to place an order for a volume license. To find a reseller in your area, go to http://partners.adobe.com/resellerfinder/na/reseller.jsp.

Electronic licensing
You must accept the license agreement and warranty terms to use this product. See www.adobe.com/go/eulas for details. This product may automatically attempt to activate over the Internet. See www.adobe.com/go/activation for details.

Registration information

Creating an Adobe ID registers your software. Please register to get up-to-date product information, training, newsletters, and invitations to Adobe events and seminars.

Known issues

Please refer to http://www.adobe.com/go/flex4_sdk_releasenotes for Flex 4 SDK known issues

AIR: Project
FB-25251 Can’t install AIR file exported from Builder – “Air file is damaged” error when previous version of AIR application is installed

Workaround: Uninstall previous version of the AIR application

ASDebugger

FB-25724 Installed Adobe Flash Player Is Not a Debugger when Flash Pro CS5 is installed and using the standalone player (no HTML wrapper)

Workaround:Uninstall your current Flash Player and run the debugger player installer found atINSTALL_DIRECTORY/players/. For the standalone Flash Player, launch the Stand Alone Flash Player found in INSTALL_DIRECTORY/players/ and open a swf to re-associate that version of the standalone Player

FB-24607 When debugging in Internet Explorer 8 on Windows 7, Internet Explorer may display a dialog when your Flash application has halted at a breakpoint. This is caused by the fact that Internet Explorer thinks the Flash Player is hung, when in fact the Flash Player is simply waiting for a message from the Flash Builder debugger.

Workaround: You can disable this Internet Explorer warning by making a change to the Windows registry. (Note, this change will affect all Internet Explorer windows, not just ones being used to debug Flash Builder applications.)

- Run regedit.exe

- Navigate to the following registry key: HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main

- Edit > New > DWORD (32-bit) Value

- For the name of the new value, type “HangResistance”

- The value in the right-hand column will show up as zero; leave it with that value.

FB‐16779 Flash Player error may occur when debugging in Google Chrome. If you want to debug your Flash applications in the Chrome browser, Chrome may see the following message when you are halted at a breakpoint in the Flash Builder debugger:
The following plug-in is unresponsive: Shockwave Flash
Would you like to stop it?
It is normal for the Flash Player plug-in to be unresponsive when you are at a breakpoint. To prevent Chrome from displaying this message, modify the shortcut that you use to Chrome. In Windows, right-click on the shortcut and choose Properties. Go to the Shortcut tab, and append “–disable-hang-monitor” to the “Target:” field.

ASDoc – Display

FB-25623 No ASDoc for unsupported locales in plug in build using non bundled eclipse distros

Adobe Community Help

FB-26153 Context-sensitive help for ActionScript Language Reference is not displayed on first invocation. Workaround: Windows: Select Adobe Community Help > Edit > Preferences. Then select Local Content > ActionScript 3.0 Reference and click the update button. OS X: Launch Adobe Help > Preferences. Then select Local Content > ActionScript 3.0 Reference and click the update button.

Compiler

FB-26001 /SDK-25513 Incremental compiler fails to pick up metadata changes. Fix is scheduled for SDK 4.1. Workaround: Perform a full compile.

SDK-25619 Embedding font in a library throws compile time error. Fix is scheduled for SDK 4.1.

FB-25787 Cannot use the -static-rsls option in “Additional compiler arguments” input

Workaround:In the project’s properties dialog, go to “Flex Build Path” and choose “Merged into code”.

FB-24955 Compile error when a package named ‘style’ contains a CSS file that’s referenced by an MXML file in the same package as CSS

Workaround:Rename the the ‘style’ sub-package to something else, and there’s no error.

Installer

FB-21960 FB Plug-in doesn’t launch on certain machines

Workaround: in eclipse.ini file, change the memory allocation to;

-Xms80m

-Xmx256m

FB-26159 Uninstalling ColdFusion Builder deletes the Flash Builder RDS plugin. Workaround: Close ColdFusion Builder perspectives prior to uninstall or reinstall Flash Builder.

FB-26047 unable to install FB Plug-in into external eclipse 3.4.2 when language pack is not installed (Japanese Only)

Workaround: Install the Japanese Eclipse language pack.

FB-15844 FB Plug-in not supported on eclipse3.5 cocoa on mac

FB-25217 Flash Builder installation not supported on Windows OSs where the user name has 4-byte characters.

Project Definition

FB-12261 project that contains modules, and uses -resource-bundle-list compiler option do not list any bundle names derived from [ResourceBundle()] metadata tag

Workaround: if you build large project with many modules, edit the .actionScriptProperties file and comment the modules, build the to generate the bundles.txt. copy the bundles.txt to other location and uncomment the modules to compile the whole project without overwriting the bundles.txt. Everytime you add resourcebundle, you have to repeat this process

Project: Import/Export

FB-26119 FXP import does not update source path when using linked folders

Workaround:Fix .actionScriptProperties file manually or re-add the source path in the project properties UI. For a consumer of a new FXPL, this isn’t obvious.

Refactoring

FB-25769 ASDoc is not updated when using refactor>rename and rename textual matches is checked

Miscellaneous

FB-11184 If you experience crashes while embedding fonts in CSS design view, then try embedding the font using a URL to the ttf file instead of using the system font name.

FB-23727Flash Builder intermittently hangs while opening projects.

Workaround:

Exit Flash Builder
Edit INSTALL_DIRECTORY/plugins/com.adobe.flexide.editorcore_4.0.0.272416/.options
Set the value of com.adobe.flexide.editorcore/registerCodeModelProjectsAsynchronously to true
Re-launch Flash Builder
FB-23023 Line numbers wont scroll along with the rest of the text and breakpoints etc wont show up in the AS editor if on secondary screen

Workaround:Update and patch information here http://blogs.adobe.com/jasonsj/2010/02/patch_for_snow_leopard_line_number_scrolling_bug.html.

Eclipse Update Site Mechanism (P2)

In order to install additional plug ins on OS X and Windows XP, you need to be logged in to a user account with Administrator privileges.
In order to install additional plug ins on Windows Vista and Windows 7, you must launch Flash Builder via the “Run as Administrator” context menu option and authenticate if prompted
If you are installing ColdFusion Builder or the LCDS Modeler plug ins, you will need to run Flash Builder once using a user account that is in the Administrator group on OS X or XP or with “Run As Administrator” on Windows Vista and Windows 7.

Flex Unit

FB-25586 FlexUnit fails to compile if locale is not support by Flex SDKWorkaround:Set the -locale to en_US

Network Monitor

FB-23419Suspend on startup will not suspend the network calls

FB-25589 Network monitor on – not able to make requests

Profiler

FB-23384Loitering Objects Show Zero Object References

FB-23543Safari browser crashes running profiler for the second time

FB-24111 Flash Builder Profiler doesn’t report all methods for Spark components

FB-24109 Flash Builder Profiler doesn’t report all objects for Spark components

FB-25184 Profiler does not show back references in AIR

Third Party IDE Compatibility

FB-19703 Unable to install Flash Builder plug-in properly into Zend Studio 6.1.2 standalone. The recommended workaround is to install the Flash Builder plug-in into the All-In-One Eclipse PDT + Zend Debugger Plug-in (http://www.zend.com/en/community/pdt). An alternate workaround (not recommended) is to rename the “dropins” folder to “links” and restart Zend.

DCD: LCDS

FB-22755 Cannot use update method which has changes – public void updatePerson3Params(Person person, Person prev, ArrayList changes)

DCD: PHP Introspector

FB‐19657 optional arguments not displayed after introspection

FB-19046 PHP Introspector can fail when authentication is enabled on the web server (like IIS)

DCD: Configure Return Type

FB-22805 Auto guess not working when service is created using Generate a Sample link

FB-24640 : [WSDL] Configure Return Type and Test Operation for WebServices is not allowing Date input format

Flex Automation

FLEXENT-792: Very low level of control on the pointing hand movements if you use object spy and move over Flex components in an Air application.

DCD: Service Wizard

FB-24162: [SDK][Dependent][Static XML] RTE occurs as auto CRT incorrectly parses xmls with empty data type

GB18030 support for Windows XP

In order to support the display of all characters of the Chinese standard GB18030 on Windows XP systems, Adobe recommends the installation of the Microsoft GB18030 Support Package. This support package will update an XP system with, among other things, fonts and input-method-editors (IMEs) to correctly support GB18030. The support package is available as a download from the Microsoft website.

Customer care
Customer Service

Adobe Customer Service provides assistance with product information, sales, registration, and other non-technical issues. To find out how to contact Adobe Customer Service, please visit Adobe.com for your region or country and click on Contact.

Support Plan Options and Technical Resources

If you require technical assistance for your product, including information on complimentary and fee-based support plans and troubleshooting resources, more information is available at http://www.adobe.com/go/support/. Outside of North America, go to http://www.adobe.com/go/intlsupport/ click on the drop down menu under the question “Need a different country or region?”, choose a different country or region, then click GO. Alternatively, you can click on Change beside the country name at the top of the screen to select a different country or region.

Free troubleshooting resources include Adobe’s support knowledgebase, Adobe user-to-user forums, Adobe Support Advisor and more. We are continually making additional tools and information available online in order to provide you with flexible options for resolving issues as fast as possible.

Other resources

Online Resources

For complete Help plus community-based instruction, inspiration, and support, go to www.adobe.com/go/learn_Flex_support_en

Adobe Flash Builder Product Information

Flex Developer Center

Flex Developer Center Documentation

Free Flex-in-a-Week training

Tour de Flex – Sample code and Examples for Flex

3rd Party Products and Projects supporting Flex

Adobe TV

Flex User Forums

Adobe User Groups

Adobe Marketplace and Exchange

Training

Adobe Certification Program

Adobe Partner Programs

Find an Adobe Authorized Training Center

© 2010 Adobe Systems Incorporated. All rights reserved.