Top 10 Pet Peeves About FlexBuilder 3

10. I can't use relative paths in my ActionScript Build Paths settings. Therefore it is not possible to share project files between Macs and PCs.

9. "Cannot access a property or method of a null object reference." I see this error way too often. Dear compiler, please tell me which object is null so I don't have to waste time poking around in the debugger to figure it out.

8. Data Binding is wonderful... except when it doesn't work the way you want it to. For example, you can't use an XMLList as a data provider for a ButtonBar component.

7. SOAP is supposedly supported, but the auto-generated code is messy and problematic to maintain. Worst of all, some SOAP services simply do not work unless you hack the auto-generated code.

6. Upgrading Flash Player on your machine can ruin Flex's connection to the debug version of Flash. There should be UI within FlexBuilder that lets you specify which Flash Player .exe to use for debugging.

5. "Copy non-embedded files to output folder." I hate this "feature". If you're running within SVN, it will corrupt your SVN meta-files. This setting should be off by default.

4. Does embed syntax really have to be so clumsy? I mean, really, this sort of thing is just plain ugly, and is very difficult to explain to newcomers.
[Embed(source="mask.swf")]
[Bindable]
public var maskSWF:Class;


3. Displaying the hand cursor for Flex components = Major Annoyance. Why do I have to set 3 properties? And seriously, why would a BUTTON component not default to buttonMode="true" ???

2.
What this incredibly unhelpful dialog box is trying to tell you is that you tried debugging an Air app. while a debug session was already running. I'm not sure why Eclipse can't kill the old session at this point.

1. "An internal build error has occurred. Right-click for more information." Needless to say, right-clicking does not provide any useful information. It's time to restart Eclipse.