Flash Builder 4 Content-Assist / Code-Hint Bug
Working with a Beta anything can be frustrating at times ( read: a LOT of times). The Swiz Framework and Flash Builder 4 Beta have been no exception.
The latest issue I’ve stumbled upon was so frustrating I had to blog about it: the content assist (or code-hinting) in Flash Builder just seems to not work for some packages – most notably, the Flash packages.
After trying many different things, I finally discovered a message in the Adobe forums:
“The latest builds of SDK 4.0 have been updated in preparation for including playerglobal.swc for Flash Player 10.1. Flash Builder Beta 2 can not find playerglobal.swc due to the addition of the {targetPlayerMinorVersion} variable found in the flex-config.xml file.
When using recent nightly SDKs with Flash Builder Beta 2, please modify them as follows:
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
When you restart Flash Builder, we will now find a correct location for playerglobal.swc, allowing for code hints and many other features to work properly.
Jason San Jose
Quality Engineer, Flash Builder”
There are a couple of instances of {targetPlayerMinorVersion} in the flex-config so remember to remove both.
My flash packages now show up again in the content-assist context menu and all is right with the world 
Recent Comments