| Author |
 Topic  |
|
|
Christof Schardt
Junior Member
21 Posts |
 Posted - Jul 17 2026 : 03:25:21 AM
|
Time and again, I come across this phenomenon, which appears to be a bug:
In the FindSymbol-window VA doesn't show my structs and classes properly regarding the setting "defined in the current solution".
Consequence: i have to try both settings "defined in the current solution" check on AND check off, to find certain symbols.
Example:
The TranslateText.h/cpp files are part of the solution.
Among other things, they contain these two structs:
- AISessionConfig
- TranslationConfig
The first struct is listed in the "FindSymbol"-window when checked "defined in the current solution".
The second struct is not listed and I have to remove the check to find it.
Despite the are declared and defined in the same files, the are displayed differently.
This happens to many of the symbols in my huge project (900k lines).
BTW, this is the main reason, why I was hurt by the recent change in the GUI of FindSymbol. I really
need direct access (view and change) to this setting in the Find-Symbol-Window.
|
|
|
feline
Whole Tomato Software
United Kingdom
19396 Posts |
Posted - Jul 17 2026 : 08:55:29 AM
|
Would it be possible to get hold of a copy of the header file that declares these two structs, purely for testing purposes? I am wondering if there is something odd in the file that is somehow confusing our parser. I appreciate this is often not possible at all, but am asking just in case, especially since if the bulk of the code is in the matching cpp file the header file its self may not be too sensitive.
If this is possible, can you please send me the files via email:
[email protected]
including this thread ID or URL in the description, so we can match it up.
This is purely an educated guess, but I am wondering if AISessionConfig is declared first in the file, then a "strange" macro is declared, or used, and then TranslationConfig is declared. Locate and comment out the macro, and the problem with TranslationConfig not being picked up will disappear.
If something like this is happening, there are a couple of methods I can show you for hiding the macro from our parser, to "fix" the problem.
Another thought, is there more than one symbol called "TranslationConfig" in your solution and stable include directories? That could also, perhaps, be a factor.
Ideally we need to work out why some symbols aren't being listed and fix it for you, especially since if our parser is getting confused, you will probably run into other problems as well. But its going to need some more details. |
zen is the art of being at one with the two'ness |
 |
|
| |
Topic |
|
|
|
Bug in Find Symbol?
