{"id":2978,"date":"2023-02-15T12:46:31","date_gmt":"2023-02-15T16:46:31","guid":{"rendered":"https:\/\/blog.wholetomato.com\/?p=2978"},"modified":"2023-11-28T03:07:35","modified_gmt":"2023-11-28T07:07:35","slug":"visual-assist-2023-1-released","status":"publish","type":"post","link":"https:\/\/www.wholetomato.com\/blog\/visual-assist-2023-1-released\/","title":{"rendered":"Visual Assist 2023.1 released"},"content":{"rendered":"

The first update to Visual Assist for 2023 is here. This update features an extensive list of improvements and bug fixes for a variety of users. And if you haven’t, download the latest release here<\/a>. We hope you find them useful!\u00a0<\/span><\/p>\n

Improved parser auto type deduction for pointers<\/span><\/h2>\n

This release updates how Visual Assist handles auto type specifiers, particularly when reference is coming from a pointer. Previously, there was a change that when auto assignments are used, any flags (such as const) may be ignored. With this release, VA now has better pointer deduction avoiding such instances.<\/span><\/p>\n

Parser support C# tuple deconstruction<\/span><\/h2>\n

This update is useful for those using the C# equivalent of the previously released tuple deconstruction for C++\u00a0 to avoid verbose initialization of variables.<\/span><\/p>\n

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

What this update does is that when you assign multiple variables at once using a predefined struct, VA will be able to recognize those variables. Consequently, this allows its features such as syntax highlighting and navigations to function properly.\u00a0<\/span><\/p>\n

Add parser support for C++ 17’s structured binding from a constructor<\/span><\/h2>\n

This is a simple fix for an edge case for structured bindings that happens when a constructor is used. Similar to the last fix on tuple deconstruction, what this update does is that when you use the auto function to assign variables from a struct, it will now function properly even when a constructor is called.<\/span><\/p>\n

Support for custom shader file extensions<\/span><\/h2>\n

When we added shader language and HLSL support, one of the most prominent user requests was to be able to enable support for non-standard\/custom shader extensions.\u00a0<\/span><\/p>\n

\"custom<\/a>

With 2023.1 you can now add custom files by adding the extension in a text field under Options ->> VAssistX ->> Game Development ->> General<\/em>.<\/p><\/div>\n

Better code formatting and behavior for Unreal Engine copy-paste<\/span><\/h2>\n

Users can recall that when typing Unreal-specific code, there is unintended indentation behavior as a result of VS not understanding UE specifiers such as UFUNCTION and UMACROS.\u00a0\u00a0<\/span><\/p>\n

With Visual Assist enabled, the automatic indentation present in default Visual Studio is disabled. And in this release, we\u2019ve improved on this behavior by extending it to copy-paste. What this means is that when copying or cutting blocks of Unreal Engine code, the pasted code will still have the correct indentation in place.<\/span><\/p>\n

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

New UI in Find References results<\/span><\/h2>\n

Previously, when using find references<\/a>, the default scope of the search was the currently opened project or file<\/a>. This update is for those who found that results shown by find references<\/i> seem to be incomplete\u2014 it is now more apparent that you have the option to specify the scope of the search (ie. just the open project or the entire solution).<\/span><\/p>\n

\"\"<\/a>

In this release, there is a newly added notification after every search that prompts the user to redo the operation for the whole solution.<\/p><\/div>\n

Code inspections for <\/span>bugprone-inaccurate-erase<\/span> and <\/span>bugprone-bool-pointer-implicit-conversion<\/span><\/h2>\n

Lastly, we\u2019ve added two new code inspections based on clang tidy for <\/span>bugprone-inaccurate-erase<\/span><\/a> and <\/span>bugprone-bool-pointer-implicit-conversion<\/span><\/a>.<\/span><\/p>\n

The first one is useful if you use <\/span>std::vector<\/span><\/i> and you are using <\/span>remove() <\/span><\/i>or <\/span>erase() <\/span><\/i>which often uses hard to read\/type syntax. This inspection<\/span> makes sure that when you use <\/span>erase()<\/span><\/i>, it works properly.\u00a0<\/span><\/p>\n

The second one is useful when <\/span>you have a pointer as an argument to an <\/span>if statement <\/span><\/i>(or anything resembling a bool). This is because it has to be dereferenced first or else it will default to a True<\/em>. This check notifies the user if the pointer has not been dereferenced.\u00a0<\/span><\/p>\n

Both of these checks are useful because in both of these instances, the code will still compile successfully\u2014giving a false impression that everything would work as intended.<\/span><\/p>\n

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

We also have a couple of bug fixes. And although they are small bugs, we hope this would be beneficial to users who encountered problems around the following:<\/span><\/p>\n