Flex 3.2 & 3.3 Framework Issue w/ Eclipse Plugin

Question

Hey Guys,
I'm having an issue with using the 3.2 and 3.3 frameworks with the eclipse plugin (not an issue with the stand alone flex builder) (eclipse v3.3.2).  Pretty much everything works but the code hinting and auto importing doesn't work on some items.  For example anything in the "flash" package structure (ie: Event) will not import, and even worse within actionscript files, if the imports are manually typed out, the next time it does auto import something it'll actually run clean up on the file and delete the manually typed imports.  Also when typing out in mxml certain components, for example an mx:Button, the code hinting will not recognize certain attribues such as "click".  At compile time all is well and works fine as long as everything is manually typed in there.  Of course to really be an efficient coder manually typing and retyping certain imports over and over is not the answer.
Thanks in advance!
~Jamie

Answer 1

I've been using the FB Eclipse plugin (with Eclipse 3.4 and SDK 3.2.0) quite a bit and haven't had this problem at all, so I'm just taking a stab in the dark here to try to help.  It sounds to me like there might be an incorrect setting in your Flex Build Path properties or something related.  Make sure your project has the correct Flex SDK selected in the Library path, and make sure all the .swc files are showing up underneath it.  In particular, look for playerglobal.swc (that's the file that contains e.g. flash.events.Event).
If that doesn't help, you really need to provide a little more information in your question, like:
What have you already tried doing to fix the problem?  (For example, have you completely uninstalled and then reinstalled the Flex Builder Plugin since switching SDKs?  I didn't need to do this the last time I upgraded the SDK, but I'd say it's worth a try, since the installation process is pretty painless.)
Have you changed any of the Flex settings in Eclipse?
If you're working with a project you created previously, have you tried creating a brand new Flex project in Eclipse to see if the problem persists in a new project?