Irritating FlexBuilder 3 errors/bugs
I finally got my upgrade info for FlexBuilder 3 and got it installed yesterday. I then proceeded to import my project from FlexBuilder 2 and everything went really smooth. I got all of my linked resources set up and began coding. After the CS3 install debacle I was thinking "wow that went really smooth". And the install went great. However as I try and get back into my project and writing code I have noticed a few weird issues that i can seem to figure out how to fix.
The first annoying bug is that I cant ctrl+click on a class name and navigate to that class unless I force FlexBuilder to import a class via code completion first. Once I do that then the class names become clickable by holding down the ctrl key. However even when i do that, once I click on the class name I get an error notifying me that "The file you chose is not inside a project...".
But it is, its part of the linked resource classes that I have as part of the project. Ahh this is irritating.
Then the last annoyance (so far) is now when I have code problems, FlexBuilder's problems panel will show the error and the line its on, but under the Resource column it just shows the project name and the Path column is completely blank... yeah that's helpful 
I'm considering downgrading back to FB 2.01 at least until this project is done. If anyone knows how to fix it let me know, It would be much appreciated!
View my LinkedIn profile
Become a fan on Facebook
October 29th, 2008 at 7:23 pm
I’m having the same problem with the blank path. It seems to happen for me when I try to use a source path to include files that are referenced in a folder outside the normal project.
December 4th, 2008 at 5:34 am
I’m having the same dialog box error and I haven’t been able to find a solution.
December 15th, 2008 at 4:08 pm
looks like its oxygenxml
December 23rd, 2008 at 12:20 pm
I would like to help you, but I dont understand the origin of this problem If all was at the first time good.
I just can say It works great
Hopefully you found already a solution, because so far I can see, It happend a few months ago!!!
December 17th, 2009 at 8:50 am
Hi,
So? What is the solution?
I have the same problem now in FB3.3 in an AIR project.
In other dozen Flex projects I was never seen it before.
December 17th, 2009 at 9:20 am
Gabor, for me I believe it was due to a conflict with SVN. I did a fresh Checkout of my files that were under version control and that seemed to do the trick.
Hope that helps,
-Dave
January 23rd, 2010 at 3:28 pm
Dave, thanks for the tip on the missing Problems view “path”.
For me, it seems to be because the project name and directory name were mis-matched
(initial upper-case problem on Windows)
renamed the project and directory, now Problems path is working again!
March 13th, 2010 at 6:39 pm
I can’t say that differing directory/project name doesn’t also cause this problem, but it can also occur when the names are not different, as I’m seeing now. Combined “flex/java” project with flex_src files INSIDE the project – yet it complains the files aren’t in a Flex project.