I am using Eclipse.
I have opened a project that contains errors. Here is an example of the errors:
When I hover over the symbol on the left to get more information, I get a dialogue box and the error is automatically highlighted, like this:
When I click away from the error, the highlighting still persists, like this:
This will happen for multiple errors, Like this:
I would like to disable this feature. How would I do so?
For further information, I am using:
Eclipse Version 2019-12 (4.14.0)
Build id: 20191212-1212
Operating System is:
centos-release-7-7.1908
The theme is what the IDE defaulted to upon first execution, pictured here:
Upon Changing the theme to "classic" the issue persists, but with different syntax highlighting:
I have scraped through all settings pertaining to syntax highlighting in the IDE. I recognize that the theme displayed as the default theme was pertaining to window coloring as well. When changed, it still did modify the colors for syntax highlighting.
Related
I noticed that when debugging with vscode, the "variables" disappeared from the side bar, and instead shows up in the editor. Is there a way to change this?
I tried going into settings and searched for debug, but I didn't dind any settings related.
I was playing with VS code settings (I wanted to explore VS Code) and suddenly the code editing got changed. Previously the code was more colourful and there were different colours for different keywords. Now my code is mostly white. Please help me to get back to default code formatting settings.
To revert the settings completely, open the settings JSON file by bringing up the command palette (Ctrl+Shift+P) and running the command Preferences: Open Settings (JSON). Delete everything in there and save the file.
However, you might just have switched to a different theme by accident. To check that, open the theme chooser (Ctrl+K, T) and try the other themes.
I've created an application using Microsoft Foundation Class library (MFC) using the project creation wizard. I created a multiple-document interface (MDI) application. The wizard creates dummy toolbars and menus that you can work with. I extended the default toolbar with no issue however now when I try to edit it through the resource view, I get "Unknown Bitmap Format" and the toolbar doesn't open. I haven't changed the file outside of Visual Studio therefore I'm unsure as to what causing this. The toolbar still opens and works fine when the application is running, its just now I can't edit it. The Error Message
I can't seem to find a solution anywhere. The only other similar post I can find is here http://www.databaseforum.info/2/8/1e1b848b13ed1254.html however no solution has been found for them.
I've had the same error, using bitmaps exported from GIMP - and I found this post (which I haven't still tried):
https://www.curlybrace.com/words/2013/08/30/exporting-visual-studio-compatible-bitmaps-from-gimp/
When exporting bitmaps from GIMP, two options must be selected in order for the bitmaps to be compatible with Visual Studio:
Under Compatibility Options, check “Do not write color space information”.
Under Advanced Options, select “R8 G8 B8” under 24 bits.
I recently switch to eclipse CDT(Oxygen.1a Release (4.7.1a)). I also installed the DevStyle Plugin. Since then I don't get error/warning highlighting in the build console. It seems that the error is parsed correctly, because it shows up in the problem window.
Here are some pictures:
Error in Build
Problem Window
Settings
Thanks
Ok found the problem. Devstyle used black color in default for highlighting warnings and errors. With the new settings it is working.
console settings
I am running VS Code version 1.17.2 on Ubuntu 16.0.4 on a VMware Player VM in Windows 10. I installed the C++ extension for VS Code. When installing the extension there was a message to say that the extension installed OK but afterwards there was a lot of repeated messages saying something like "failed to update database".
When I type something which is invalid syntax there is no red squiggle and if I press Ctl-Space it just shows "Loading..." but nothing comes. The red flame icon on the status bar shows and I see "Updating Intellisense..." when I hover the mouse over but the icon doesn't ever seem to go away.
If I #include a non existent header, there is no green squiggle but if I save the file, exit VS Code and reopen, them the green squiggle shows on the header but there is no light bulb showing in the left margin.
I had exactly the same problem. I've been playing around with settings and disabling/enabling the extension. Finally got it working with setting the followings then disabling/enabling the extension (reload VS code after both of them):
"C_Cpp.errorSquiggles": "Enabled",
"C_Cpp.intelliSenseEngine": "Tag Parser",
"C_Cpp.loggingLevel": "Information"
Also you can play around with "Reset IntelliSense Database" command, I ran it a couple of times, that might have helped too.
I suspect the intelliSenseEngine setting was the one that made the trick.
Edit
This doesn't enable all features, e.g. wrong include markers and "go to definition" works for includes, but code completion doesn't.
I had exactly the same problem, running ElementaryOS on VirtualBox. As per this comment (https://github.com/Microsoft/vscode-cpptools/issues/756#issuecomment-303513360) I changed my settings to
"C_Cpp.intelliSenseEngine": "Tag Parser"
And things seems to be working again.
I am running VS Code 1.19.2 with C/C++ IntelliSense 0.15.0 (Microsoft) on a Ubuntu 16.04 LTS running as a Virtualbox VM (Windows 10 host). All x64 OS's.
In my case the symptom is a recurrent flaming icon in the bottom status bar hinting "Updating IntelliSense..." that seems related to a hung process.
A couple of "Microsoft.VSCod" processes doesn't use CPU...
Hovering over code just hints "Loading...".
After changing "C_Cpp.loggingLevel" to "Information" to analyze log on the Output windows (as requested in https://github.com/Microsoft/vscode-cpptools/issues/1291 thread) didn't show anything useful... but symptom dissapeared most of the time.
After changing "C_Cpp.intelliSenseEngine" to "Tag Parser" things went much better. The flaming icon disappeared and definition are available all the time.