Since I got FDT, I've been having trouble with the Help menu. I have been used to FlashDevelop, where you select a property or method in your code, click F1, and the entry in the Actioncript Dictionary comes up for reference.
I set up my Key Binding in FDT to do the same - to bring up the Help Search. However, after I clicked F1 in my Help search menu, it refused to search the "Actionscript 3.0 Language and Component Reference", even though it was checked off in my Search Scope. It only searched the "Local Help". Several sites suggest I re-import the help menu in a certain way for CS4, or to update my help in the FDT preferences. However, even after I did this, and even though I could that see these help folders were indeed in the FDT file system, it refused to search them. It was really frustrating, and I resorted to having it do a custom Google search in that window in order to get up the language reference.
I had given up, but decided to do a quick Tweet requesting help. Special thanks to hfug and the Hawaii Flash User group for responding to the request. He suggested some of the import fixes I had read before, and sent some screenshots showing the Dictionary was indeed imported into FDT. The imports fixes hadn't worked in the past, but I noticed a minor thing in his screenshot - He was showing the Help Contents, and not the Help Search. My Contents were also showing the Dictionary, so I figured if I could at least bring up the Contents with F1 instead of the Search, I could then manually select the method I was looking for. I searched the Key Bindings to see if I could do this, but the only other options listed under "help" in the Key Bindings brought you to an FDT Help webpage. So I removed the Key Binding all together.
And for some reason after that, when I clicked F1, the selected method was brought up in the help panel as if it was searched for.
No idea why....
During some research on FDT tips, I found out from here that FDT saves local histories of your files. And using these, you can compare versions. To get to this, Right Click on the file > Compare With > Local History.
I haven't tried it yet, but you can apparently also restore deleted files here as well.
While doing some coding using components recently, I noticed FDT was having trouble finding the fl.controls.comboBox, which didn't make a lot of sense to me. I was unable to data type my variables, and had no access to the component methods. I ended up just data typing it as *, which is something I hate to do.
After a bit of research, I found out that FDT cannot distribute the fl.* package, as it falls under some other licensing agreement (or something along those lines).
Luckily, I found a few people who have set up the fl.* package as a swc, so it can be set up as a linked library in FDT, which makes life a lot easier. Some of the swc files dont include certain components, but this one at apdevblog.com seems to be working for me so far: