| T O P I C R E V I E W |
| Uniwares |
Posted - Mar 16 2022 : 07:07:45 AM
Its kind of annoying that something like this still occurs:
|
| 9 L A T E S T R E P L I E S (Newest First) |
| Uniwares |
Posted - Mar 22 2022 : 06:49:55 AM
If I find anything new about this, I let you know. As mentioned already, this is a huge, antique, code base, although pretty straight forward and simple. But there are some classes with the same name in different namespaces/projects, although not the one in this topic. |
| feline |
Posted - Mar 22 2022 : 06:33:59 AM
That really isn't that helpful. It seems something confused our colouring code. Since it is designed to run fast it is certainly possible to confuse it, but normally that is due to the same symbol name being used for different types of symbol, so you can understand why it happened.
Without a sample to prod, I am not sure what else we can do here, but I suspect you will see this again. I would just like to know why. |
| Uniwares |
Posted - Mar 21 2022 : 08:16:16 AM
Looks like the symbol definition is ok. no duplicates or alternative definitions. But, to make things funnier: after restarting the IDE and reloading the project, the coloring is once more correct. |
| feline |
Posted - Mar 21 2022 : 08:02:06 AM
It is worth mentioning the tooltip colouring problem with Find References Results. This is a known problem, it is actually OS dependent. Just when you think we only need to consider the IDE version.
case=141555
For the colouring of "FrontEndSettings", this suggests that something in this block of code is confusing our colouring parser.
If you open VA's Find Symbol dialog and search for:
.FrontEndSettings.
where the blue marks start and end of a symbol name, so we will only get exact matches, and turn Off both check boxes at the bottom of the dialog, is the symbol coming back with different types? Or is there only one result for this symbol?
I am trying to work out what might be leading VA to work out two different colours for the same symbol name. |
| Uniwares |
Posted - Mar 18 2022 : 1:35:48 PM
Interesting: when I side scroll until the word "FrontEndSettings" is only half visible, all instances are colored in gold, and then remain like this even after scrolling back. |
| Uniwares |
Posted - Mar 18 2022 : 1:32:22 PM
There are a few hundred in this file, but it seems they are all the same as a find in files shows the same number.
Context/definition field shows the right thing. What I noticed though is that its kinda slow to color those "FrontEndSettings", there is a visible delay before they get colored over the default VS coloring.
PS: should I complain that the tooltips in the VA Find References window are plain ones, with light background and no syntax coloring? |
| feline |
Posted - Mar 18 2022 : 1:00:54 PM
Can you please try Find References, probably Find References in File for speed, on this function, and see if all of these entries are being picked up?
Is VA's context and definition field showing the same thing for both coloured versions of the function?
Since this is so stable it almost suggests its deliberate, but if so there should be some other differences as well. |
| Uniwares |
Posted - Mar 18 2022 : 08:46:48 AM
Yes and yes. Compiles fine, no errors, not even warnings.Its old code, ancient to be precise. Scrolling doesnt affect either. |
| feline |
Posted - Mar 18 2022 : 08:25:45 AM
That doesn't make much sense. Is this stable, if you change files or scroll past this block?
Assuming this is stable, perhaps a stupid question, but does the code currently compile? Sometimes code you are still writing can confuse our parser. We try not to let this happen to often, but its inevitable at times. |
