breadcrumb arrow home | blog

Flex 3 quirks

Posted: 28/12/07

An image of Flex 3 quirks

Here's a couple of minor issues, and their associated fixes, that I've noted for Flex Builder 3.

If you choose not to install the bundled debug player over the top of your existing player, and then do it yourself after the installation, the minimum player version requirements aren't automatically updated. When you run your application, you see the default AC_FL 'No Flash' HTML, and no Flex app.

You need to change the player version number manually by: right-click->properties on your project folder; select ActionScript Compiler; then update the Require Flash Player version with the correct minor version.

I've also noticed that Flex Builder 3 sometime does import classes for you; particularly if you've been working in the IDE for a good few hours. Helpfully, if you then manually add these imports into the top of your classes, it will remove them! I'm not sure whether this has something to do with the memory heap becoming excessively large over time, causing Flex Builder to 'tire-out', or whether there is a genuine issue with the auto-import feature.

You may also experience the recurring "internal build error" message in the problems panel. I've found that in most cases this can be resolved by adding and then deleting a character from a class in your app, then saving again. This forces the IDE to rebuild again, and normally removes the message. Weird!

Flex 3 on Adobe Labs

Keywords for this post: flex 3, flex builder, flash player version