Forum Replies Created
-
AuthorPosts
-
Ophidian14Participant
Yes!! It works. Thank you.
Ophidian14ParticipantThat honestly would be a lifesaver.
Ophidian14ParticipantOkay, but is there any way I can get it to ignore unknown options? Instead of re-formatting in a completely wrong way?
June 7, 2020 at 07:16 in reply to: Is #include_next supported in Intellisense path searching? #28353Ophidian14ParticipantThank you, the problem ended up being my ordering of Intellisense directories.
May 24, 2020 at 17:21 in reply to: How to prevent VisualGdb from changing colors in visual studio #28196Ophidian14ParticipantOkay, well thanks.
May 24, 2020 at 06:17 in reply to: How to prevent VisualGdb from changing colors in visual studio #28194Ophidian14ParticipantSorry to resurrect an old post but I basically have the same question. I recently installed VisualGDB build 3595 into VS2017 and opened a C++ project. The default color for many kinds of text (such as: C++ member function) was changed from black to a sort of maroon color (red 128, green 0, black 0). It’s listed as the “default” on this screen: https://imgur.com/a/fPlX7oF My question is what is causing the default color to change, and how can I revert the colors to the way they were? I didn’t understand the advice to export/import settings, especially since they’ve already been changed now and I have no way to go back.
Ophidian14ParticipantAlso I’d like to ask a slightly different related question. I follow the following steps:
- Create a new Linux Cmake project targeting C++17.
- Manually add the /opt/rh/…. include paths for devtoolset-8.
- Add #include <optional> and declare a std::optional<int>.
- I seemingly have to restart my project for the changes in #2 to correctly reflect in #3 (otherwise my usage of optional is red underlined and unrecognized) but I am not worried about this.
At this point I change from Cmake build to Custom build step. Immediately I lose support for C++17 and std::optional, they go red squiggly and the error console says “namespace std has no template optional” or something like that. My question is, why does changing the build type lose me the C++17 support and how would I reintroduce it?
Ophidian14ParticipantI don’t understand what was requested or what was changed but would like to. I did static_cast< [Ctrl-Space] but just see a very long list of suggestions including things that are not types. Can you provide an example of how to use this?
Ophidian14ParticipantThank you!! The fix works.
Ophidian14ParticipantHad a semi-related followup question. I recently upgraded to build 2753 and in my project properties I see three choices for Intellisense engine. Clang (default), VS2017, and “Advanced Clang Intellisense”. I know what ‘VS2017″ is, but what’s the difference between the other two? Is it what you could switch off about six months ago by clicking the Stopwatch icon and disabling…. something? I can’t remember exactly what it was.
Ophidian14ParticipantSupport contract is renewed. Thank you for any assistance you can provide.
Ophidian14ParticipantIs there an option to disable where you hover over something and it pops up the “Find All References” box automatically? This functionality is not performant on my project and it spins up CppEngineHost64.exe to 100% and this locks up my machine.
Ophidian14ParticipantI’m at 100% CPU, so much so that it slows down/almost locks up my computer at times. I got the estimated time to display but the time just keeps going up and up. One time I let it run overnight and when I came in the next morning, and tried to use it, it just started over and tried to rebuild it from scratch again. What policy governs how this cache is invalidated?
Attachments:
You must be logged in to view attached files.Ophidian14ParticipantI would also like to disable this as it’s useless in my project, “updating global symbol cache” never completes even after an hour, I also noticed that the “estimate” of time remaining has been removed.
Ophidian14ParticipantWhat were the threats?
-
AuthorPosts