Shulou(Shulou.com)06/02 Report--

Today, I will talk to you about how to use the new Editor function in Visual Studio 2013. Many people may not know much about it. In order to make you understand better, the editor has summarized the following for you. I hope you can get something according to this article.

In the Editor of Visual Studio 2013, we introduced a series of new features designed to increase productivity and save time. Some of them are new features, while others come from Productivity Power Tools's popular extensions. The addition of these features is due to feedback from users' friends through User Voice suggestions, forum posts, and Connect errors. The MVP community is also helping us in the choice of expansion projects.

In the new version of Editor, our main concern is to ensure that developers do not have to leave the current editing environment as much as possible. The features described in this blog post will easily provide the necessary information while allowing you to stay in the current code position.

Peek Definition (Alt + F12)

As we all know, developers often need to walk back and forth in the code when browsing the definition. When designing the features of Visual Studio 2013, we carefully considered how to use elements and gestures to help developers browse the definition without losing their current code location. Peek Definition is one such feature that allows people to view definitions inside Editor without opening new document tags. To experience its actual effect, you can right-click a symbol, click the "Peek Definition" command from the shortcut menu, or press the shortcut key combination Alt+F12 directly.

Using Peek Definition can help us save time on understanding the code base because it allows users to view relevant definitions without having to divert attention from the current code. We can even browse a series of related definitions without departing from the original file. When you call the Peek Definition command in the current Peek view, the system guides you to view the definition inside the Peek view and adds the return navigation in the previous Peek view. These return navigation elements can help you intuitively understand how you have reached the current definition step by step.

When designing this feature, we chose to build on the concept of "Preview Tab" that appeared in VS 2012 because the Peek view is a temporary display of results designed to help people avoid opening more documents. Returning to navigation is another bootstrap we have added, hoping to help you understand the navigation stack visually while continuing to face the current code. In fact, if you hover over the return navigation, the system will prompt you with a small piece of code so that you can quickly know where you are being directed.

In the Visual Studio 2013 preview, Peek views have read-only properties. After testing by internal users, we found that you clearly wanted to be able to edit the Peek view-- of course, we started to implement this requirement immediately. Please pick up the official version and experience it immediately.

Enhanced scroll bar (Enhanced Scrollbar)

The enhanced scroll bar (Enhanced Scrollbar), which has always been an extension of Productivity Power Tools, is now officially a standard member of Visual Studio 2013. The enhanced scroll bar provides users with visual clue information on the vertical scroll bar. The markers on the scroll bar can help you quickly view errors, warnings, breakpoints, bookmarks, the location of search results, and other useful information in files. Similarly, we hope to enhance the scroll bar to help users learn more about the results of the prompt at the current location-- without having to drag the scroll bar to the corresponding location.

Map mode

We added a "map mode" (Map Mode) to the scroll bar to bring some cool features-and you can customize the mechanism:

1. A 10000-foot view of the code-take a macro look at the code, making the scroll bar a powerful tool to help us clearly understand the structure of the code.

two。 Click scroll-click any area in the scroll bar to direct everyone to the corresponding location in the file-this is a new mechanism to quickly locate the content of the file.

3. Preview specific parts of the file-hover your mouse over any location on the scroll bar to preview the contents of the corresponding section in the prompt. This feature will bring a convenient experience during the document review process.

Navigate to (Ctrl+,)

In the process of exploring to improve development productivity, we try to move away from traditional independent tool windows and modal dialogs to seek a smoother direct experience to help people focus on coding rather than managing Visual Studio. We analyzed the usage data and decided to update the navigation to (Navigate To) mechanism, so that this set of modal dialogs, which are still widely used, can be climbed to another story.

With the new navigation to function, you can enter any part of the symbol content and use intelligent semantic search to find its definition. You can also type a part of the file name to quickly switch to the corresponding location-whether or not the file has been opened before.

The navigation to feature in Visual Studio 2013 supports all the features of earlier versions, but instead presents in a smoother, unmodeled, and space-efficient manner. We place the new search window on the upper right around the search area in the editor. This layout allows us to display the preview tab while increasing the number of navigation to the results without obscuring the preview code view.

The results of the selection are automatically displayed in the preview tab. This helps users to ensure that the selected result is the object they are searching for, thus making a better judgment before submitting it to the new view. To make it easier for everyone to return to their original location, we can simply press the Esc key to cancel the jump results-which avoids the positioning troubles that can be caused by search results errors.

In designing these features, we want not only to improve the performance of the original runtime, but also to improve the workflow. The new navigation to function is optimized for keyboard operation, that is, refer to the browsing focus of Solution Explorer. In the process of function development, we detect and analyze the actual usage of internal users, so as to test whether the new function design has actual efficiency. Next, please learn about the statistics we refer to.

We counted the number of times users used the "down arrow" button on the keyboard, and used the results as a basis for judging the accuracy of the prompt list:

The data show that in most cases, users simply press the enter key-which means that the search query is located accurately. Some users press the "down arrow" button more than 15 times while browsing the results, which has nothing to do with accuracy-it's just that they find a large number of results.

In order to determine whether to continue to turn on the navigation function when the user clicks on an area outside the results list, we count the number of times the user keeps it open. After investigation, we found that the average duration from the moment the dialog box opened to the moment it was closed was six seconds: the data showed that in most cases, users only need to press enter directly-which means that the search query is accurately located. Some users press the "down arrow" button more than 15 times while browsing the results, which has nothing to do with accuracy-it's just that they find a large number of results.

In order to determine whether to continue to turn on the navigation function when the user clicks on an area outside the results list, we count the number of times the user keeps it open. After investigation, we found that the average duration from the moment the dialog box opened to the moment it was closed was six seconds:

This reflects the two most common operations: the user navigates to a new location and starts browsing, or cancels the operation. This result led us to decide to close the navigation to the dialog box after the user clicked on another area. We will continue to focus on using data to ensure that this design is intuitive to most users.

Automatically complete parentheses

The automatic completion parenthesis function, as the name implies, automatically completes the closing parentheses, quotation marks, curly braces, etc., for the code we enter in the editor. This is also a popular feature from Productivity Power Tools, which we have now officially introduced to Visual Studio 2013.

We have also added completion rules for different types of languages. For example, in C++, we will automatically complete the literal representation of the original string of Category 11 and use the "* /" as the closing tag of the C-type comment, while inserting a semicolon in the class type.

Up / Down move (Alt+ up / Down Arrow)

The up / down move feature allows you to quickly move one or more lines up and down, such as the Alt+ up arrow and the Alt+ down arrow. This is another popularity extension in Productivity Power Tools, which also adds Visual Studio 2013 this time.

New IDE feature for Visual C++

We have also added a number of new features for Visual C++. In the coming weeks, the Visual C++ technical team will share more information on their blog. Please stay tuned. In today's article, however, we want to emphasize the C++ code format.

The C++ editor can now automatically adjust the format as you enter, which also works on code that is pasted directly into the C++ file. We have found that there is not a widely accepted coding style for C++, so we have added a flexibility option to our settings to allow you to customize the environment to match your own development style. We look forward to your feedback so that we can make further adjustments to the settings.

New IDE features for JavaScript

In JavaScript, we have added identifier highlighting-now when you select an identifier (such as a variable name or function call), the reference to it will be highlighted in the current source file. We have also set up a new navigation bar to display the relevant content at the top of the editor window, so that you can more easily switch back and forth between the main function and object in the JavaScript source file.

After reading the above, do you have any further understanding of how to use the new Editor features in Visual Studio 2013? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.