- This topic has 6 replies, 2 voices, and was last updated 4 years ago by
.
-
Posts
-
Hi,
VisualGDB can display many different windows, depending on what you are doing. You can find detailed description of most of them in our documentation, tutorials and the list of settings.
If VisualGDB is not working as expected, please provide a complete description how to reproduce the issue from scratch per our problem reporting guidelines and we will try to point you to the relevant setting. Please make sure you include the relevant screenshots, as they often contain important information required to pinpoint the issue.
The problem is the automatic correction (intellisense) suggesting all kind of options while you are typing and every variable or cast I enter is changed. This has so much effect that the editor is almost of no use. Visual Studio describes how to switch it off, but this does not seem to work for VisualGDB. I just want to type without being interrupted by wrong suggestions. I added a picture.
Think I found the option in Tools->C/C++ (VisualGDB)->advanced->Code Completion->Suggest names while typing. Set it to False. (Still can use Ctrl+J to get IntelliSense suggestions)
When I add a include file to my source a very annoying popup occurs. Listing loads of include files.
How can I stop this popup from appearing?
Also the pop-up is only partial visible because it goes of my screen.
Please don’t add more clutter to the editor it cost so much time to clear all this kind of stuff.
Hi,
As you have pointed out before, you can disable the suggestion popups via Tools->C/C++ (VisualGDB)->advanced->Code Completion->Suggest names while typing.
You can also try setting Tools->Options->Text Editor->C/C++(VisualGDB)->Advanced->Code Completion->Smart Suggestion List GUI to VS2019+ Native that is somewhat slower than the VisualGDB-provided one, but will work better on high-DPI displays.
You can disable the Code Explorer (Outline and Globals views) by unchecking the “Show window on startup” setting as shown here.
- You must be logged in to reply to this topic.