freelance developer of javascript, python and more!

I’m using a nightly build (currently 13493) of the Flex SDK to build my current due to some bug fixes that my project needed (there was a problem with the [Managed] decorator not working). However, the new builds broke the autocomplete functionality in Flash Builder.

I was able put up with it for a week. The lack of autocomplete was manageable, it was the fact that it also broke the import organisation that was infuriating. For example, I have a custom event class that extends flash.events.Event. I had to manually insert the ‘import flash.events.Event’ line into the file, but every time I used autocomplete for a valid class, Flash Builder would delete the import because it couldn’t find the Event class in any library.

I spent quite a while googling to find an answer to the problem but came up empty handed. So I started having a root around the sdk, comparing it with the build shipped with Beta 2. In new builds, the flex-config.xml file contains reference to the targetPlayerMinorVersion variable . It seems that Flash Builder is unable to handle this, so could not resolve the playerglobal.swc library containing all of the base classes.

After finding this, one quick search led me to a post on the Adobe forums that contained a description of the problem and the answer:

  1. Rename the folder <nightly sdk location>/frameworks/libs/player/10.0 to “10″
  2. Edit the file <nightly sdk location>/frameworks/flex-config.xml and remove “.{targetPlayerMinorVersion}” and save

I hope this helps anyone having the same problem!

§24 · January 22, 2010 · Flash Builder · · [Print]