Refactoring
- Rename
- Extract Method
- Encapsulate Field
- Change Signature
- Move Implementation to Source File
- Add Member
- Add Similar Member
- Document Method
- Create Declaration
- Create Implementation
Writing Code
- Suggestion Lists
- Acronyms
- Shorthand
- Surround Selection
- Insert of }, ), ]
- VA Snippets
- Format after Paste
- Multiple Clipboards
- Insert _ after m and Shift
Reading Code
- Enhanced Syntax Coloring
- Local Symbols in Bold
- Stable Symbols in Italics
- Highlight Matching {} and ()
- Column Indicator
- Highlight Current Line
Search and Navigation
- VA Outline
- Find References
- Find by Context
- Goto
- List Methods in File
- Open File in Solution
- Find Symbol in Solution
- Open Corresponding File
- Most Recently Used List
- Navigate Back and Forward
- Move Scope
Corrections
- Underline Spelling Errors
- Underline Mistyped Symbols
- Highlight Mismatching {} and ()
- Repair Case
- Convert Dot to ->
Enhanced IntelliSense
- Enhanced Listboxes
- Parameter Info
- Hovering Tooltips
- Hovering Class Browser
- Context Field
- Definition Field
Configuration
Features for VC6
Definition Field
Click on any symbol and see its definition at the top of your source window. The Definition field works in concert with the Context field to give you more detailed information for a symbol.
When not on a symbol, the Context field contains a yellow arrow and identifies your current scope. The Definition field contains details of the scope. For example, when you are within a for statement, the Definition field contains the for condition.
When at global scope, the Definition field contains the full filename with path of the current file.
When on a symbol with multiple definitions, the dropdown arrow at the right of the Definition field opens a list of all definitions.
Icons
Icons in the Definition field describe symbols. They are identical to those in the Class View.Classes
Public methods and functions
Protected methods
Private methods
Public members and variables
Protected members
Private members
Preprocessor macros
C/C++ Headers
When the caret is on a #include statement in C/C++, the Context contains the base name of the header and the Definition field contains the full path of the header. The path you see is the one Visual Assist X uses to find the header, which is typically the same one used by the compiler.
If Visual Assist X finds the incorrect header, you should correct the problem by updating your IDE settings or the Directories node in the Visual Assist X options dialog.
Evaluate All Macros
For C/C++ users, definitions reflect moderate evaluation of preprocessor macros during parsing of definitions. In this way, Visual Assist X displays definitions in meaningful terms; definitions are not evaluated to base types alone. For example, the Definition field tells you UpdateData() returns aBOOL, not a long, despite the fact BOOL is a typedef for a long.
By default, Visual Assist X does not evaluate preprocessor macros that do not take arguments, i.e. not created with (). You see the name of the macro in the Definition field.
You can force Visual Assist X to be more aggressive in evaluating preprocessor macros during parsing of definitions. When in this mode, preprocessor macros are evaluated as deeply as possible. You see base types in the Definition field, and in hovering tooltips.
Copying a Definition
Right+Click in the Definition field to copy its content. The other items in the Right+Click menu do not serve any useful purpose.
Top or Bottom
Specify the location of the Context and Definition fields in the options dialog. Disable the feature, or eliminate the Navigation Bar in the IDE, to conserve the space in your source windows.
Miscellaneous
The Definition field describes the current selection when scrolling through listboxes.Clicking on an unknown symbol makes the Definition field go blank.
The separator between the Context and Definition fields is movable.