Moved to Using Flash Builder
Do you mean something like this:
That works fine for me. Can you post a code snippet?
Jason San Jose
Software Engineer, Flex Mobile
Thanks for the quick reply, Jason.
Here are two screen shots showing that in MXML the Code assist DOES work:
and in <fx:Script> it does NOT:
Just to reiterate: this is OS 10.6.4; the workspace is default, i.e. Documents/Adobe Flash Builder Burrito Preview/
Curiously, the Code assist is working just fine in the release Builder, even with 'Hero' SDK.
Thanks for looking into the issue.
That works for me too. Do you have anything in your error log? ~/Documents/Adobe Flash Builder Burrito Preview/.metadata/.log. Alternatively, press CMD+3 when in FB and type error log. Select the first entry to open the Error Log view.
There's a way to get code hints to fail, but it took me 2 sequences of "." and backspace at the end of that line. I assume you're just typing "btn."?
You'll need to enable showing hidden files in Finder. Yes, cascaded is part of the workspace. Try opening the error log view via CMD+3 (see above).
I don't see any indication in your error log of a code hints problem. You've mentioned that the implicit "." member access isn't triggering code hints. What about CTRL+Space explicitly after "btn."?
Try a clean workspace. It's odd that your first cycle says "templates". We've seen something similar in the prerelease where users had stale preferences. File > Switch Workspace > and choose another location.
Changing the workspace to new one solved the problem!
Can't help to ask: are there any settings in the default workspace that I could correct to use it, or just forget about the default and use new custom workspace?
Regardless, thank you very much, Jason.
1 person found this helpful
You might try going into preferences under Flash Builder > Editors > ActionScript Code > Content Assist Cycling and hit restore defaults. If that doesn't work, you're better off with the clean workspace.
Hitting 'Restore defaults' did solve the problem.
Just to be clear: I have NOT changed these defaults.
thanks once again,
A clean workspace resolved the issue for a little bit but then the problem returned. Can this problem be fixed officially w/o a workaround?