![]() ![]() I suspected the issue could be caused by the "Parse all files when opening a project" option, so I tried with this option both checked and unchecked, and the behavior still occurs. I _think_ the issue didn't occur on Visual Studio 2017 (but I also switched codebases when I switched to VS2019, so maybe that's also part of the issue).įor context, our solution has 84601 files (as reported by the "Open File in Solution" dialog). ![]() I am currently using the following version, and the issue still occurs: I've seen this behavior happen for at least 6 months now, at least since the following version, on Visual Studio 2019: "VA_X.dll file version. ![]() If I then try the same with a symbol "S3", the issue occurs yet again. At some point, after repeating the process multiple times (or simply waiting for a while before trying again), Visual Assist properly locates "S2". Even if I go back to file A again, and move the caret again on "S2" (or select the whole symbol "S2"), and hit Alt+G again, Visual Assist keeps locating "S1" instead, and does that for a while (at least several seconds). However, it happens very often that if I go back in file A, then move the cursor to another symbol "S2", then hit Alt+G again, Visual Assist still opens file B and locate "S1", instead of locating "S2". Let's say I put the caret on a symbol "S1" in file A, then hit Alt+G: this opens file B and properly locates the symbol "S1". selection issueįor a while now, I've experienced an issue when using Alt+G (VAssistX.GoToImplementation) after changing the caret position or the selected word in the Text Editor (in C++). Whole Tomato Software Forums - GoToImplementation (Alt+G) vs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |