{"id":3218,"date":"2023-05-17T12:00:51","date_gmt":"2023-05-17T16:00:51","guid":{"rendered":"https:\/\/blog.wholetomato.com\/?p=3218"},"modified":"2023-11-28T03:07:09","modified_gmt":"2023-11-28T07:07:09","slug":"visual-assist-2023-2-released","status":"publish","type":"post","link":"https:\/\/www.wholetomato.com\/blog\/visual-assist-2023-2-released\/","title":{"rendered":"Visual Assist 2023.2 released"},"content":{"rendered":"

The second update to Visual Assist in 2023 is here. This update features an extensive series of upgrades to code inspections, shader extension support, and a number of quality fixes to the IDE. Download the latest version<\/a> of Visual Assist now.<\/span><\/p>\n

Greatly expanded code inspections with over 100 new Clang Tidy checks<\/span><\/h2>\n

The biggest item in this release is the added support for all code checks available from Clang Tidy. Code inspections are semi-automatic checks that prompt the user when Visual Assist\u2019s engine recognizes outdated syntax or an otherwise correctable code issue.\u00a0<\/span><\/p>\n

For context, Visual Assist\u2019s code inspection<\/a> is based on a series of checks from LLVM Clang Tidy. And before we add support for a new check, we rigorously test it for accuracy and compatibility. This process ensures that the check will give consistent suggestions for almost all use cases. In fact, this is the process undertaken for the two new added code inspections<\/a> in this release\u2014more on them later.<\/span><\/p>\n

What we\u2019ve added is the ability to use <\/span>unevaluated Clang Tidy checkers as Code Inspections straight from Visual Assist. This greatly expands the types of code issues that can be detected with code inspections enabled. There is a slight tradeoff in that you may need to do some manual testing<\/a> when using unvetted checks. Take a look at the full documented <\/span>list of Clang Tidy checks<\/span><\/a>.<\/span><\/p>\n

The latest addition to our list of vetted code inspections are for <\/span>bugprone-swapped-arguments<\/span><\/a> and <\/span>bugprone-argument-comment<\/span><\/a>. <\/span>These checks look for potentially swapped arguments by looking at implicit conversions and detect typos in argument comments and suggest automated fixes for them<\/span>, respectively.<\/span><\/p>\n

Lastly, we\u2019re also announcing that code inspection is officially out of beta and is now running on Clang engine version 15.0. The beta label is mostly a formality and all functionality should function the same. If you haven\u2019t, we highly advise <\/span>enabling code inspections.<\/span><\/a><\/p>\n

\"group<\/a>

Protip: When running comprehensive code inspection checks in a file, you can sort and group issues by level. Code inspection levels refer to an arbitrary metric representing severity given to a code check. Level one signifies critical, level five being on the level of a reminder, and zero refers to unflagged checks.<\/p><\/div>\n

Extended Shader File Customization<\/span><\/h2>\n

\"Visual<\/a><\/p>\n

Due to consistent demand and great feedback, a significant portion has also been given to further improve our support for shader files. In fact, as of this release, it is in the last phases of beta testing and will most likely be available for general support very soon.<\/span><\/p>\n

In this release, you can now use custom shader file extensions (there are no longer extensions considered \u201cdefault\u201d). Coloring and syntax highlighting has also been drastically improved, with almost all bugs ironed out as well.<\/span><\/p>\n

Enable support for shader file parsing by accessing<\/span> Visual Assist Options ->> Game Development ->> Enable support for shader files.<\/span><\/i><\/p>\n

\"Enable<\/a><\/p>\n

Integrated-style extensions menu (pre-Visual Studio 2019)<\/span><\/h2>\n

In Visual Studio 2019, the toolbars and plugins were rearranged<\/a>. Instead of being able to access your plugins in the main toolbar, you had to instead go under the Extensions menu.\u00a0<\/span><\/p>\n

For the most part, this made sense\u2014it\u2019s easier to find all installed plugins and access their features correspondingly. However, for users who had one or a handful of plugins or are more comfortable using the mouse instead of shortcuts, the extra step might be bothersome (e.g. mouse users with only VAX installed).<\/span><\/p>\n

Some users expressed interest so we\u2019ve added the option for an integrated-style menu for extensions (similar to the pre-VS 2019 setup).\u00a0<\/span><\/p>\n

\"\"<\/a>

This new menu mode can be enabled via Extensions ->> VAssistX ->> Visual Assist Options ->> Display ->> Switch to Legacy Style Main Menu<\/em>.<\/p><\/div>\n

Implement Virtual Methods context menu option to check \/ uncheck all.<\/span><\/h2>\n

The last of the new features in this release is a quality of life change. Inheriting from other classes is made much easier and intuitive using the <\/span>Implement Virtual Methods<\/span><\/a> feature.<\/span><\/p>\n

While in the dialog, we added a small tweak that allows users to check and uncheck all possible methods using a simple checkbox. Neat little addition, we hope.<\/span><\/p>\n

\"\"<\/a>

Visual Assist’s Implement Virtual Methods feature provides a neat little dialog to make inheriting from other classes quick and intuitive.<\/p><\/div>\n

 <\/p>\n

Bug Fixes<\/span><\/h2>\n