If you don’t read our build change history page, you might miss some small gold nuggets. For example, back in build 1734, we added an enhancement to our goto command (alt+g) so that it operates within comments. The accuracy of goto within comments depends upon uniqueness of identifier name and context of the comment, and there will be plenty of cases where it can’t figure out what you want it to figure out, but it works enough to bring it to your attention.
Archive for the ‘VA X Features’ Category
I was using the OFIS (Open File in Solution) dialog the other day and it occurred to me that I use some features in it that might not be so apparent to users that didn’t actually write the code for it. As an aside, this feature was formerly known as Open File in Workspace (or OFIW) before Workspaces were replaced by Solutions in Visual Studio.NET. It took us a few years after the release of Visual Studio.NET to get around to updating the name (I supposed we had to accumulate a few “What’s a workspace?” queries from new users before making the update).
At any rate, here’s a tip for the OFIS dialog: you can use the Up and Down arrow keys as well as the Page Up and Page Down keys to navigate up and down through the file list while focus is still in the edit control. No need to tab around or click in the list to change the selection after having typed in the edit control to filter the list.
This also applies to the Find Symbol in Solution (FSIS) dialog.
In our latest builds of Visual Assist X, we’ve been sneaking in some enhancements from our work on the upcoming Visual Studio 2010 beta. We decided to roll these features out early so our users could start enjoying them in currently supported IDEs with out having to wait for the full VS2010 beta. Hope you enjoy!
Enhanced suggestions are one of the items we’ve added.
VA now offers smarter suggestions based on types in assignments, conditional statements, method arguments and return values. For example, when assigning to a variable “v = “, VA will suggest other variables of the same type from the current scope. For certain types such as bool, VA will also suggest relevant values (“true” and “false”). In method calls, VA looks at the method signature and makes suggestions based on the type of the current argument. Suggestions are also offered for return values, based on the method’s return type.
Enhanced suggestions are influenced by scope. For example, VA suggests case/break/default in switch statements and private/protected/public in class definitions. Within a switch statement on an enum, VA suggests the enum items in the case statements.
You may also notice that our suggestions as a whole are less noisy, take up less screen real estate and are more accurate. They contain less of the stuff you will likely never type and better guesses at what you are likely to type. Suggestion listbox tooltips only display once you pause typing, reducing distraction and saving valuable screen real estate, yet preserving the additional information for when you need it. We hope you like the changes!
Give the latest build a try and tell us what you think.
We recently released a feature for C/C++ that has long been requested: Add Include. A lot of work had previously been put into our #include completion listboxes – but that work is moot because now you don’t need to type #includes directives by hand.
The Add Include command is available when you place the caret on a symbol which is declared in a header file that is not directly included in the active file.
If the header that the symbol is defined in is already directly included in the current file, the command is disabled. Otherwise, it is enabled – even though the dependency may already be satisfied by another directive that itself #includes the header. This is by design as many programming style guidelines mandate explicit inclusion of declarations (as opposed to happenstance or indirect inclusion).
For types and functions, Add Include straightforwardly adds an include directive for the header in which the type or function is declared. For variables that are declared in the active file, Add Include acts on the type of the variable (no need to go to the declaration of the variable to add the include for its type). For variables that are not declared in the active file, Add Include operates in the same way as it does for types and functions.
While the command is available in the usual VA Refactor menus, the easiest way to invoke it (at least for keyboardists) is to place the caret on a symbol and press alt+x, r, n.
Several members of the Whole Tomato Software crew attended the Seattle XNA Gamefest held back in July. It was a great opportunity for us to get face time with quite a few of our customers. We received a lot of feedback some of which has bubbled up in VA X 10.5.
We learned that many Visual Studio users only work in the IDE for editing and debugging but not for doing builds. Because it is not being used for builds, people are working with solutions that are empty or are incomplete, adhoc file collections.
To address editing and navigation productivity in these scenarios, we have added optional support for directory based file discovery. If enabled, VA X will scan for files that are in the same directory as any opened file. Newly discovered files (those which are not already explicitly listed in the solution) are treated as part of the solution in the eyes of VA X. The files are listed in the VA X file lists (OFIS and VA View) and symbols declared in them are listed in the VA X symbol lists (FSIS and VA View).
File discovery is controlled via two settings on the Projects|File Handling node of the VA X Options dialog. The first setting enables this support for only when the loaded solution is empty. The second enables it independently for when files are present in the loaded solution. The first setting is enabled by default whereas the second is disabled. If you use partial solutions as described above, then we recommend enabling the second option.
In order for VA Snippets to be offered to you while you are typing, make sure that the “Include VA Snippets in listboxes” setting is enabled on the Advanced | Suggestions page in the Visual Assist X Options dialog.
VA Snippets are managed using the VA Snippet Editor. The editor can be accessed via the “Edit VA Snippets” button on the Advanced | Suggestions page or by invoking the “VAssistX.VaSnippetEdit” IDE command (using the View | Other | Command Window). VA Snippets are defined independently per file type so that, for example, snippets with VB comments will only be available in VB files.
Assign shortcuts using the VA Snippet Editor. Shortcuts are simple alphabetic text, unlike standard keybindings which use Ctrl/Alt/Shift modifiers. Example shortcuts are:
When you type a snippet shortcut in the text editor, VA will add the snippet to the suggestion listbox. If you accept the suggestion, the shortcut that you typed will be replaced with the snippet.