Accessibility

Flex Release Notes

Flex 1.0 Updater 1 Release Notes

The Macromedia Flex 1.0 Updater 1 includes performance and reliability improvements, enhanced documentation for the Flex ActionScript and MXML API Reference, and more.

Creating new SWC files for Custom Components and Themes

If you created any custom components or custom theme files based on the FlexForFlash.zip file, and exported them to SWC files from Flash MX 2004, you have to export them again to create new SWC files using the version of FlexForFlash.zip included in the Flex Updater 1 release. For more information on using FlexForFlash.zip, see the chapters "Using Styles, Fonts, and Themes" and "Working with Flash MX 2004" in the "Developing Flex Applications" book. If you have not already done so, the chapter "Working with Flash MX 2004" explains how to configure Flash MX 2004 to create SWC files using the FlexForFlash.zip file.

Fixed Issues

The following issues have been fixed in Flex 1.0 Updater 1:

89812 UIObject no longer creates a memory leak.

89584 The format="xml" attribute on WebService.operation.request was not working with binding.

89312 The RemoteObject tag with a protocol of AMF now ignores objects of type java.lang.Class rather than throwing exceptions.

89129 When a data-bound Repeater object was used as part of a pop-up window, it was not being destroyed even after the pop-up window was closed.

88810 Accordion containers were handling focus management incorrectly.

88700 The deletePopUp() method is now available on any subclass of UIObject. Previously, it was only available for Window and Panel containers.

88695 The mxmlc command-line compiler now returns a more informative error message if the -configuration option points to an invalid configuration file.

88680 Errors are more descriptive when users incorrectly attempt to set styles using ActionScript.

88470 The showEffect and hideEffect effects were not working for ProgressBar controls.

88134 The XMLDecoder was not handling multiple arrays correctly.

87988 The fdb command-line debugger was displaying "Trial Edition" even when Flex was running under a commercial license.

87853 Setting the selectedIndex property of a ComboBox control was not updating the drop-down list.

87837 When launching a TitleWindow container as a pop-up, using the x and y properties in ActionScript caused a visual separation of the drop-shadow from the TitleWindow.

87755 When selecting Sunday for Day of the Week, the DateFormatter returned undefined if three or more pattern letters were used. With one or two pattern letters, the DateFormatter returned the correct Day of the Week digit.

87581 The Flex Web Service and HTTP Service proxies now allow requests to be routed through an external HTTP proxy server. For authenticating HTTP proxy servers, the Web Service and HTTP Service proxies support Basic and NT domain authentication. You configure the authentication settings in the flex-config.xml file using the <external-proxy> tag, as the following example shows:

<web-service-proxy>
  ...
  <external-proxy>
    <location>server:8080</location>
    <username>username</username>
    <password>pwd</password>
    <nt-domain>domain</nt-domain>
  </external-proxy>
  ...
</web-service-proxy>
          

The <location> tag defines the server name and port to use as an HTTP proxy. Specify the <username> and <password> tags when the proxy server uses BASIC authentication. Specify a value for <nt-domain> when the proxy server uses NTLM authentication. You must explicitly add the <external-proxy> and its child tags to the <web-service-proxy> and <http-service-proxy> definitions in order to use authentication for the proxies.

87569 ActionScript Profiler data was not being correctly generated when ProfileFunctionEnable was set to 1 in the mm.cfg configuration file.

87534 When a client requested an MXML file and the <User-Agent> HTTP header was missing or was empty, Flex threw a NullPointerException. Now Flex ignores the missing header.

87505 MXML components can now implement interfaces, as the following example shows:

<mx:HBox xmlns:mx="http://www.macromedia.com/2003/mxml" implements="MyInterface">
          

87457 You could not export the Slider control (extras/slider/SliderSource.fla) in Flash MX 2004 when the classpath pointed to the Flex classes.

87351 The Explorer Session sample application was failing on Tomcat 5.

87332 The <mx:HTTPService> tag was not sending data on Tomcat or WebLogic servers for POST methods when noProxy was false, and contentType was application/x-www-form-urlencoded. On Tomcat and WebLogic servers, Flex now adds the parameters to the request body by default. If you experience this problem when using another application server, set the flex.addFormParameters JVM property to true; for example, in your jvm.config file, add the following argument:

-Dflex.addFormParameters=true
          

To turn off this behavior for WebLogic and Tomcat servers, you must explicitly set the value of flex.addFormParameters to false in your JVM configuration file.

87284 Error alert boxes for WebService and HTTPService were not popping up on root, when the faulty service was in a child of a navigator.

87276 Flex was throwing a java.lang.StringIndexOutOfBoundsException exception when the value of an XML node was a single hyphen character ("-").

87217 When dynamically binding data to a TextArea component, null values were not clearing the component; the previous non-null value was still displayed.

87214 There was an error reading variable values when debugging with the Flash Debug Player. Variables referenced by parent object and variable name (for example, myObj.myVar) were not being returned, whereas variables referenced by only the variable name (for example, myVar) were returned.

87206 The browser detection logic was not forwarding Netscape 7.1 users to the correct page when no Flash plug-in was installed.

87123 The speed of tabbing between text fields in the FlexStore sample application has been improved.

87035 The credit card ComboBox in the Flex Store sample application was not working correctly when the user navigated with a keyboard.

86863 The Flex Web Service and HTTP Service proxies now support the pooling of HTTP connections. You configure connection pooling for these services in the appropriate section of the flex-config.xml file by adding a <max-connection> tag. If the tag is not present, then Flex uses the default value of 50 connections. You can change this number by adding a <max-connection> tag to the <web-proxy-service> or <http-proxy-service> settings, as the following example shows:

<web-service-proxy>
  ...
  <max-connections>25</max-connections>
  ...
</web-service-proxy>
          

To disable connection pooling, set the value of <max-connection> to 0.

84069 The width of DataGrid components was increasing slightly after they were loaded.

78995 The ActionScript Profiler was causing a memory leak in Flash Debug Player.

 

Getting Started

 

Application Development

 

Security

 

Downloads

 

Documentation

 

Community Resources