I am currently testing Flash builder 4 beta 2 and what I am facing right now is code hinting that comes with pressing ctrl+spacebar.This feature is sometime shown by my Flash builder but sometime it doesn't show anything
What I am trying to say is that say I launched Flash builder now and it is showing the code hinting with press of ctrl+spacebar.Now I close the flash builder and again relaunch it ,then the same code hinting doesn't show at all even if I press ctrl+spacebar.
Any user facing this situation.
Do you see an error dialog or anything in your workspace log? <workspace location>/.metadata/.log
There is a intermittent known bug in Beta 2 https://bugs.adobe.com/jira/browse/FB-21566 that you may be seeing.
Jason San Jose
Quality Engineer, Flash Builder
Code hints are one of the most frequently used features of any IDE. In this release, we've made several subtle changes to how code hints work to improve usability and productivity.
The proposals in the code hints popup now display more descriptive information.
use namespace mx_internalor
this.mx_internal::...) code hints will show proposals for definitions in those namespaces.
Sometimes while writing MXML, you just want to see the list of available properties of a particular kind. For example, you would like to see all effects supported on
s:Button. This kind of filtering behavior is now possible with proposal cycling in MXML.
To see this in action, open the code hints popup and press Ctrl+Space again after the popup is open (see Figure 3). By default, the next cycle you will see is All Properties (or Properties if you happen to be in an attribute scope). The name of the current cycle is displayed at the bottom of the popup. If you continue pressing Ctrl+Space until you see Effects, then code hints will shown only effects properties.
By default, the cycle order is as follows:
You can reorder or turn off proposal cycling by opening the Preferences dialog and selecting Flash Builder > Editors > MXML Code > Advanced.
To help with the transition from MX to Spark components, MXML code hint proposals now indicate when a component has been replaced with an alternative. If you trigger code hints for a component that has a replacement in Spark (for example,
mx:Button), code hints will display “use s:Button instead” (see Figure 4). Also, “s:Button” will appear below the proposals for
In an SDK 4 MXML file, if you look for hints on a component that doesn’t exist, the code hints will propose valid alternatives. For example, if you look for
s:HBox, code hints will propose both
mx:HBox as potential matches (see Figure 5).
The Flex SDK naming conventions use a camel case pattern for nearly all identifiers. Flash Builder 4 beta 2 uses the capital letters that denote word boundaries to accelerate code hinting (see Figure 6).
For example, instead of typing mx:AdvancedDataG to see all tags that start mx:AdvancedDataGrid, you can simply type ADG and the code hint proposals will be filtered as you would expect. The same applies to properties and attributes. For example, from a UIComponent, type eMin to show
explicitMinimumWidth. Note that each segment is matched from the beginning.
Camel case support is available in the ActionScript and MXML editors as well as the Open Type dialog (Ctrl+Shift+T).
Several ActionScript and MXML language features are newly supported in code hints:
HostComponent], and so on have an attribute that specifies a fully qualified type name. These references are now recognized and support features you would expect for a type reference, including go to definition, mark occurrences, and rename and move refactoring.
at com.adobe.flexbuilder.codemodel.internal.asdoc.ClassCommentRef.<init> (ClassCommentRef.java:36)
at com.adobe.flexbuilder.codemodel.internal.tree.ClassNode.getDynamicCom mentRef(ClassNode.java:779)
at com.adobe.flexbuilder.codemodel.internal.tree.BaseDefinitionNode.getC omment(BaseDefinitionNode.java:334)
at com.adobe.flexide.as.core.contentassist.ActionScriptCompletionProposa l.<init>(ActionScriptCompletionProposal.java:151)
at com.adobe.flexide.as.core.contentassist.ActionScriptCompletionProcess or.getTypeProposal(ActionScriptCompletionProcessor.java:691)
at com.adobe.flexide.as.core.contentassist.ActionScriptCompletionProcess or.createProposalsFromDefinitions(ActionScriptCompletionProcessor.java :952)
at com.adobe.flexide.as.core.contentassist.ActionScriptCompletionProcess or.createLocalProposals(ActionScriptCompletionProcessor.java:786)
at com.adobe.flexide.as.core.contentassist.ActionScriptCompletionProcess or.computeCompletionProposals(ActionScriptCompletionProcessor.java:114 2)
at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompleti onProposals(ContentAssistant.java:1836)
at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeP roposals(CompletionProposalPopup.java:555)
at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$1 6(CompletionProposalPopup.java:552)
at org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(Co mpletionProposalPopup.java:487)
at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProp osals(CompletionProposalPopup.java:481)
at org.eclipse.jface.text.contentassist.ContentAssistant.showPossibleCom pletions(ContentAssistant.java:1664)
at org.eclipse.jface.text.source.SourceViewer.doOperation(SourceViewer.j ava:807)
at org.eclipse.jface.text.source.projection.ProjectionViewer.doOperation (ProjectionViewer.java:1506)
at com.adobe.flexide.editorcore.editor.FlexSourceViewer.doOperation(Flex SourceViewer.java:176)
at org.eclipse.ui.texteditor.TextOperationAction$1.run(TextOperationActi on.java:131)
at org.eclipse.ui.texteditor.TextOperationAction.run(TextOperationAction .java:129)
Europe, Middle East and Africa