Intellisense Bug after Switchover

[AgAuCu_123]

Hi there,

I am having an issue with Clang IntelliSense. When I switch the default engine in the Clang IntelliSense Diagnostics Console from Clang to Native VC++ and then back to Clang, IntelliSense no longer works correctly for Clang. Native VC++ still works correctly always if I switch back.

For example, if I start typing a word, the suggestion list appears as expected. However, when I press Tab to accept a suggestion, nothing happens. Instead of completing the word, it just inserts a tab character in the text editor. The same happens when I use the Down Arrow key. Instead of moving to the next suggestion in the list, the text editor cursor simply moves down to the next line.

It seems like the keyboard input is always being sent to the text editor instead of the suggestion window. I would appreciate if this could be fixed, because I really like the possibility to use both for example for different code analysis.

Is there at the moment also a better workaround to fix this. I only know the solution to close and open Visual Studio again.

[support]

Hi,

This looks like a broken installation. Please try uninstalling VisualGDB and installing the latest version again.

[AgAuCu_123]

Hi,

unfortunately this hasn’t resolved the issue. It’s probably not related to the installation either, as I’m seeing the same behavior on two different laptops.

Here are some details about my setup:

• Visual Studio 2022
• Embedded Project
• MsBuild
• Target for example some STM32F
• VisualGDB Custom Version 6.1R3 (build 5547)

I also tested the behavior with an Advanced CMake project. Switching to Native VC++ there doesn’t seem to have any effect. I’m not sure if this is expected, but I generally prefer using MSBuild anyway.

[support]

Hi,

OK, we have reproduced the issue. Switching the IntelliSense engine from MSVC to Clang involves re-creating a few relatively complex structures required for backward compatibility. It looks like something about the order in which they are re-registered interferes with filtering of keystrokes.

You can try a couple of workarounds:

• Try changing the suggestion list GUI via Tools->Options->Text Editor->C/C++(VisualGDB)->Advanced->Code Completion->Smart Suggestion List GUI. Simpler GUI modes do not depend on the advanced filtering.
• Re-opening the file (or the entire solution) will automatically do a clean reset of the keystroke filters, so you don’t need to restart VS entirely.

That said, switching between Clang IntelliSense and MSVC IntelliSense is mostly intended for diagnostic purposes, and is expected to be done infrequently. Is there any reason you are often switching back and forth between them? We are working on a few optimizations related to caching of the sources and the Go-to-Definition command, so if you are switching away from Clang to work around issues with these commands, we might have a better fix for you.

[AgAuCu_123]

Hello,
thanks for your help. The solution with closing the file and reopen it again works fine as a workaround. I sometimes use MSVC IntelliSense because in certain situations it works better, and I also like to run static analysis from both tools.

Regarding the optimizations you mentioned: what would be the better fix?

By the way, I really like VisualGDB , it has allowed me to work on embedded projects with my usual toolchain (Visual Studio), and I just wanted to say thank you for that.

• This reply was modified 2 weeks, 3 days ago by AgAuCu_123.

[Author]

Posts