I am using Eclipse 3.3.2 with the Flex Builder Plugin (3.0.194161) and the Flex SDK 3.2. Recently the intellisense has started forgetting about everything in the flash.* package EXCEPT flash.errors.*
The code still compiles, but attempting to automatically resolve something (CTRL+SPACE) removes any of the flash.* import statements and thus causes a compile error. As it stands I have to either not use CTRL+SPACE, or re-add my flash.* before compiling.
I have tried recreating the workspace/project and have re-installed the Flex SDK, but I still get the same problem.
Any thoughts?
I was able to work around the problem by adding the following SWC to my library path: FLEX_SDK\libs\player\10\playerglobal.swc
It looks like the problem is caused by {targetPlayerMajorVersion} no longer resolving, though I have no idea how that happened.
Edit: Known bug, as described in FB-16703 and "Targeting Flash Player 10"
Upgrade to Flex Builder 3.0.2. I've noticed that older versions of Flex Builder don't like Flash Player 10's new playerglobal.swc.
Related
I have a problem with Flash, so that Flash Builder shows an error icon on my project (and I can't run my project) but there's no error I'm sure -> I's working on this project and there's not any error in it AND flash builder doesn't show any error on any file. Any helps? How can I resolve this problem?
Note: I'm using Flex SDK 4.6 and BlazeDS...
Sometimes when odd things like this happen, you can fix them by cleaning the project or the workspace.
You can clean the project by selecting "Clean" from the project menu in Flash Builder.
To clean the work space, you want to first shut down Flash Builder. Then relaunch Flash Builder using the '-clean' command line argument.
Per the comments on the original question, your solution was the latter.
Why Flash Firebug doesn't work with flex 4.5?
UPDATE:
Hy!
I have Flex 4.5 and in the main application, in the script tag I write:
import ominds.Firebug;
I use flash player WIN 10,1,85,3 Debug enabled.
I export swf as 10.1.85 version.
And when I open the flashFirebug I get this:
"No SWF files with the O-Minds package found, you should import the O-Minds package into your flash files. For more information visit: o-minds.com/products/flashfirebug"
I appreciate any help (:
I'm using robotlegs if this matters...
Check out FlashFirebug 3.0, I haven't personally tried it with Flex, but it's reported to work. Here's the product homepage
http://www.o-minds.com/products/flashfirebug
hello man just get the new update "2.0" it works with flex and even you don't need to import the package anymore, and also you can debug any swf on the web :D
Have you tried updating your debugger to the latest version? As long as you're exporting to a SWF and to a valid version of Flash, it should work. I'm using the Beta Debugger for Flash 10.2 and I have no issues using Flashbug.
I installed Flex Builder plug in (3.2) into Eclipse 3.4. The installation had no errors, but I get this error when trying to start a new Flex Project.
The selected wizard could not be started.
Plug-in com.adobe.flexbuilder.apollo.ui was unable to load class com.adobe.flexbuilder.apollo.ui.wizards.flex.FlexApolloProjectWizard.
com/adobe/flexbuilder/editors/common/ui/project/wizards/AbstractFlexProjectWizar d
I have tried re-installing several times, even tried the older eclipse versions.
Any thoughts ?
When Flex is installed on a Windows machine, it generates two versions of the Flex SDK, one in C:/Programs Files/Adobe/Flex Builder 3 Plug-in and the other in your Eclipse directory (not sure if this is true on a Mac). I've fixed similar issues by copying missing files from the Flex Builder folder into the parallel Eclipse plug-in directory. That would be my first guess.
If that does not work, you may have to contact Adobe.
Sometimes Flex is... terrible. I mean absolutely awful.
There was a major kerfluful with the fact that FlexBuilder would install correctly in Eclipse 3.4. The new Flashbuilder, for version 4 is designed to work with 3.5(galileo), I'm hoping that it will work with Helios, so I will no longer need to keep multiple Eclipse versions going. Here's a link on how to make it work. I just hope we don't have to keep repeating this.
After upgrading the Flex SDK from 3.1 to any newer version of the SDK and trying to compile an existing project, the following error appears in the Problems pane:
Description: { expected
Resource: (shows project name, not a specific file)
Location: line 15
Any ideas how to solve this or where to start the bug hunt?
It looks like the problem is in the ...sdks/3.3.0/frameworks/libs/player/10/playerglobal.swc file, but I'm certainly not sure.
I've had this happen (among others). Never got to the bottom of it. In the end I migrated my code files to a new project. There are some pretty nasty bugs in FlexBuilder, especially when working on 64bit windows.
Have you tried to do a clean on the project? You didn't mention this but I assume that the project compiles fine under 3.1? If you create a new project does it compile cleanly (if not, it may mean that you have a bad download of the SDK and need to get a new copy.)
The problem was solved by removing halo.swc from libraries. Copying halo.swc to the project was suggested by an online tutorial (which I cannot find right now).
when i open .mxml flex file in eclipse it gives error
Could not open the editor: Assertion failed:
Does any one know about it
First of all you can give which operating System and version, IDE version, Flex plugin version, detail of error message. You can try ;
Check eclipse and flex plugin version compatibility if you use flex plugin. (If you use Linux operating system flex plugin compatible with eclipse 3.3 ide if not You can try to install flex plugin on eclipse 3.3 if you use 3.4 or 3.5 and so on)
You can download full package of flex ide instead of flex plugin on eclipse
I think its better to stop searching when you are in Flash and Linux. Here in this link its very much transparent. I tried all the fix provided out there, nothing did really worked what new comers are looking for.
Details: http://labs.adobe.com/technologies/flex/flexbuilder_linux/releasenotes.html#sysreq
Note: GUI will never work, which we are thinking and Autocomplete etc will also not work. So Flash and Linux is actually useless and time lose. The best thing is keep reporting Adobe for this. Because they are counting our Linux Vote.
Try changing your current workspace to another one, it helped in my case.
If you have disabled asking for workspace at startup you can change it here:
Window > Preferences > General > Startup and Shutdown
I just got the same error, after moving my project to a new computer. Turns out the build paths needed to be changed in the new computer. After updating those it seemed to fix the problem.
I struggled with this a couple of hours: my own "solution" to this was that I had Eclipse Galilieo / Weblogic 10.3.2 / Windows 7 set up correctly, but was accidently opening an old Eclipse Helios install pointed to the same projects. In other words yes, its likely a slight path difference or a new name for an updated resource along one of your paths. "assertion failed" is such a generic exception that you could get with so many different softwares, that I thought this input wouldnt hurt...