| T O P I C R E V I E W |
| andreas.theurer |
Posted - Jan 10 2008 : 07:55:44 AM
With VAX Options->Advanced->Font and Colors->Variables you can define the color, which is used for declared variables. ( Default is grey ).
As soon as you delete the variables declaration, the variables color changes from grey to black.
I would prefer red, orange, or something similar for those undeclared variables. Which is more eye-catching than black.
Where in the VAX-Options can I change the color for undeclared variables.
Thanks in advance for your hints.
Sincerely Andy
|
| 26 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Jan 24 2008 : 08:53:53 AM
I understand the problem, and many thanks for your efforts so far.
As a very quick test, in the test project if you deleted everything in the cpp file except for the #include lines do you still see the problem?
If so then deleting chunks of "normal" looking code from the .h file may allow you to find the trigger for this problem fairly quickly.
I know how difficult it can sometimes be to find the cause of these sort of bugs. I was hoping I could do that for you, but you need to make sure the files are safe to share first.
Any help you could provide with this would be gratefully received. |
| andreas.theurer |
Posted - Jan 24 2008 : 05:06:02 AM
Thanks for help so far.
I already tried to reduce the two files ( cpp & h ), which I added to the new small test project, in that way, that I would be able to give you the code. When I removed to much code, the described error, was gone. So the thing is, I have to remove as much code, that I am allowed to give the the rest, but as less that the error still is present.
Hopefully I have in a few days a little time gap, where I can try to do this. But today unfortunately I can't invest so much time to do this.
If I find a little bit more time I can try it and can notify you again.
OK ?
|
| feline |
Posted - Jan 23 2008 : 08:51:44 AM
Are you able to send me your small test project? If so I can try the same tests here, and see if I can reproduce the problem.
Clearly something is going wrong, but I am not sure what. |
| andreas.theurer |
Posted - Jan 23 2008 : 01:26:45 AM
In both projects ( the small test project and the project from which I toke the cpp and h file ) the behavior is the same. When I add a comment with a spell error, the spell error becomes underlined.
And as I already mentioned: The mistyped symbol also becomes underlined in a single function. But not in methods of my class. |
| feline |
Posted - Jan 22 2008 : 08:56:25 AM
The file size should not matter. I have just tested underlining of mistyped symbols in a 23,000 line file, and it is working correctly for me.
VA does not attempt to underline mistyped symbols until after you have edited the file. This is an optimisation, to speed things up when you are just opening and reading code, without actually editing it.
If you copy these two files into the test project and then make an edit or two to the cpp file, and wait a couple of seconds, do you see any underlining?
Try adding a comment with a spelling error in it, see if the comment spelling error gets underlined. |
| andreas.theurer |
Posted - Jan 22 2008 : 02:32:22 AM
ok, tried to reduce the code, to be able to pass it to you.
But when I did that the mistyped string orange became underlined.
I guess the problem of the missing underlining is, that the cpp was to large ( 1958 lines of code ).
|
| feline |
Posted - Jan 21 2008 : 08:57:29 AM
Sorry, my fault. That was not as clear as it could be.
The "caret" is where you type. So if you left click with the mouse into the variable "banana" or "orange" this will place the caret or typing place into the variable.
The context and definition fields are normally at the top of the editor. This is where the alt-m list appears, if you ever use it:
http://www.wholetomato.com/products/features/context.asp
http://www.wholetomato.com/products/features/definition.asp
Would it be possible to get a copy of your test project so I can test it here please?
I understand that sharing code is often not possible. Hopefully you can delete most of the code from the cpp and .h file so it is safe to send me the files. If I can reproduce the problem here I can try to find out what is causing the problem.
If you are able to send me the project please submit the files via the form:
http://www.wholetomato.com/support/contact.asp
including this thread ID or URL in the description, so we can match it up. |
| andreas.theurer |
Posted - Jan 21 2008 : 05:54:36 AM
ok
to your first question:
Where should I place what?
What do you mean with VA context and definition fields, which fields exactly in the VA GUI do you mean?
your second question:
Yes I placed the cpp and h file of myclass in the test project, that I created earlier. The behaviour that test project is the same. ==> That means as long the function is a function, the orange is underlined. As soon as I change the function into a method of myclass the underlining of orange disappears. If I turn it back into a function again, underlining also comes back. |
| feline |
Posted - Jan 17 2008 : 08:42:48 AM
That is most odd. But also interesting, it suggests there is something about this class that is causing the issue. With the class version of the function, with no underlining, if you place the caret into "banana" and "orange" what does VA show in its context and definition fields?
Can you copy the header and cpp file you have used in this test and add then to the default project you made earlier? I am wondering if these two files on their own are sufficient to reproduce the problem, or if the problem only shows up when the files are part of your main solution. |
| andreas.theurer |
Posted - Jan 17 2008 : 12:26:27 AM
Ok, I placed your code in an new file, which I added to my project.
=> And now the mistyped string "orange" becomes underlined.
I did a further test on my own:
I placed your code in one of my source files. And also there the mistyped string "orange" becomes underlined.
When I converted your function into a class-method ( testUnderliningHere ==> MyExistingClass::testUnderliningHere ) underlining of the mistyped string disappeared. When I converted class-method back into a function, underlining of the mistyped string comes back. |
| feline |
Posted - Jan 16 2008 : 1:11:44 PM
We can probably ignore colours since this works in a new project.
It sounds like something is confusing VA in your main project. Which gets us back to some form of parser problem, as Uniwares guessed.
In your main project can you try adding a new empty cpp file, and then paste in the following code please:
static void testUnderliningHere()
{
int banana = 2;
banana = 1;
orange = 2;
}
With VA told to show local symbols in bold "banana" and "orange" should look different (only banana should go bold) and orange should be underlined as a mistyped symbol. What do you see? |
| andreas.theurer |
Posted - Jan 16 2008 : 05:21:40 AM
In a new default project underlining of a mistyped symbol works!
Custom window or IDE color scheme? Whats that? |
| feline |
Posted - Jan 15 2008 : 2:47:27 PM
Do you see underlining of mistyped symbols in a new default project? If not then it is probably not a parser problem. If you do then it is probably related to the other problems people are seeing.
Are you using a custom windows or IDE colour scheme? |
| andreas.theurer |
Posted - Jan 15 2008 : 12:21:50 PM
I already recognized that VA sometimes needs a little bit time, for underlining misspelled words, for example.
So I already waited a little bit more. ==> But the undeclared variable didn't became underlined.
|
| Uniwares |
Posted - Jan 15 2008 : 10:48:58 AM
In my opinion its VAX's slow parsing that may cause that. It seems that the parser is now a lot slower in reparsing changed code than it was, it even looks as if it would parse ALL code when the current file changes. But it might then also be related to the problems I am seeing with parameters becoming unknown.
Did you try to just wait for some time (10+ seconds) to see if VAX catches up with the changes? |
| andreas.theurer |
Posted - Jan 15 2008 : 10:13:18 AM
Showing matching brackets is working fine as well the rest of the
syntax highlighting.
Underlining of mistyped symbols is the only thing, which does not work. |
| feline |
Posted - Jan 15 2008 : 10:07:36 AM
That is a lot of directories, but I don't see that stopping underlining working. Nothing else is standing out as odd.
Does showing matching brackets work?
What about other syntax highlighting options?
Is it only underlining of mistyped symbols that you are having a problem with? |
| andreas.theurer |
Posted - Jan 15 2008 : 09:42:05 AM
---> ok,, here it is:
=============================
VA_X.dll file version 10.4.1624.0 built 2007.12.07
Licensed to:
VA X: [email protected] (10-user license) Support ends 2008.07.10
DevEnv.exe version 7.0.9955.0
msenv.dll version 7.0.9955.0
Font: Courier New 13(Pixels)
Comctl32.dll version 5.82.2900.2982
Windows XP 5.1 Build 2600 Service Pack 2
2 processors
Platform: Custom
Stable Includes:
d:\\programme\\microsoft visual studio .net\\vc7\\include;
d:\\programme\\microsoft visual studio .net\\vc7\\atlmfc\\include;
d:\\programme\\microsoft visual studio .net\\vc7\\PlatformSDK\\include\\prerelease;
d:\\programme\\microsoft visual studio .net\\vc7\\PlatformSDK\\include;
d:\\programme\\microsoft visual studio .net\\frameworksdk\\include;
Z:\\B16\\Administration\\PublicInterfaces;
Z:\\B16\\AdvancedMachiningInterfaces\\PublicInterfaces;
Z:\\B16\\AdvancedMathematics\\PublicInterfaces;
Z:\\B16\\AdvancedTopologicalOpe\\PublicInterfaces;
Z:\\B16\\AnalysisMeshingModel\\PublicInterfaces;
Z:\\B16\\AnalysisMeshingToolsItf\\PublicInterfaces;
Z:\\B16\\ApplicationFrame\\PublicInterfaces;
Z:\\B16\\AUTClmInterfaces\\PublicInterfaces;
Z:\\B16\\AUTCsm\\PublicInterfaces;
Z:\\B16\\AUTCsmInterfaces\\PublicInterfaces;
Z:\\B16\\AUTCsmPrd\\PublicInterfaces;
Z:\\B16\\AutomationInterfaces\\PublicInterfaces;
Z:\\B16\\AUTRteInterfaces\\PublicInterfaces;
Z:\\B16\\BasicTopologicalOpe\\PublicInterfaces;
Z:\\B16\\BatchInfrastructure\\PublicInterfaces;
Z:\\B16\\CAACloudQsrItf\\PublicInterfaces;
Z:\\B16\\CAACompositesItf\\PublicInterfaces;
Z:\\B16\\CAAFreeStyleItf\\PublicInterfaces;
Z:\\B16\\CATAnalysisBase\\PublicInterfaces;
Z:\\B16\\CATAnalysisGPSInterfaces\\PublicInterfaces;
Z:\\B16\\CATAnalysisInterfaces\\PublicInterfaces;
Z:\\B16\\CATAnalysisReportInterfaces\\PublicInterfaces;
Z:\\B16\\CATAnalysisResources\\PublicInterfaces;
Z:\\B16\\CATAnalysisVisuInterfaces\\PublicInterfaces;
Z:\\B16\\CATArrangementInterfaces\\PublicInterfaces;
Z:\\B16\\CATAssemblyInterfaces\\PublicInterfaces;
Z:\\B16\\CATBehaviorInterfaces\\PublicInterfaces;
Z:\\B16\\CATCloudEditorInterfaces\\PublicInterfaces;
Z:\\B16\\CATCommonLayoutInterfaces\\PublicInterfaces;
Z:\\B16\\CATCoreCavitySeparationUI\\PublicInterfaces;
Z:\\B16\\CATDataExchControlAlgo\\PublicInterfaces;
Z:\\B16\\CATFunctSystemItf\\PublicInterfaces;
Z:\\B16\\CATGraphicProperties\\PublicInterfaces;
Z:\\B16\\CATHullConceptualInterfaces\\PublicInterfaces;
Z:\\B16\\CATHVDiagramInterfaces\\PublicInterfaces;
Z:\\B16\\CATIAApplicationFrame\\PublicInterfaces;
Z:\\B16\\CATIAV4Interfaces\\PublicInterfaces;
Z:\\B16\\CATIdeSettingsInterfaces\\PublicInterfaces;
Z:\\B16\\CATInstantCollabDesignCAAItf\\PublicInterfaces;
Z:\\B16\\CATIPDAdapterInterfaces\\PublicInterfaces;
Z:\\B16\\CATMatInterfaces\\PublicInterfaces;
Z:\\B16\\CATMfgSimulationInterfaces\\PublicInterfaces;
Z:\\B16\\CATMmFunctionalInterfaces\\PublicInterfaces;
Z:\\B16\\CATMoldDesignFeature\\PublicInterfaces;
Z:\\B16\\CATMoldDesignUI\\PublicInterfaces;
Z:\\B16\\CATMoldDesignWorkbench\\PublicInterfaces;
Z:\\B16\\CATMoldInterfaces\\PublicInterfaces;
Z:\\B16\\CATMultiCADInterfaces\\PublicInterfaces;
Z:\\B16\\CATOBMInterfaces\\PublicInterfaces;
Z:\\B16\\CATPDMBase\\PublicInterfaces;
Z:\\B16\\CATPDMBaseInterfaces\\PublicInterfaces;
Z:\\B16\\CATPDMReconcile\\PublicInterfaces;
Z:\\B16\\CATPIDiagramInterfaces\\PublicInterfaces;
Z:\\B16\\CATPlantShipInterfaces\\PublicInterfaces;
Z:\\B16\\CATPlantShipModeler\\PublicInterfaces;
Z:\\B16\\CATPLMDictionary\\PublicInterfaces;
Z:\\B16\\CATPPRHubWtpImpl\\PublicInterfaces;
Z:\\B16\\CATPPRHubWtpInterfaces\\PublicInterfaces;
Z:\\B16\\CATRdgInterfaces\\PublicInterfaces;
Z:\\B16\\CATRmaInterfaces\\PublicInterfaces;
Z:\\B16\\CATRscInterfaces\\PublicInterfaces;
Z:\\B16\\CATSchPlatformInterfaces\\PublicInterfaces;
Z:\\B16\\CATSchPlatformModeler\\PublicInterfaces;
Z:\\B16\\CATSdeSettingInterfaces\\PublicInterfaces;
Z:\\B16\\CATSmaInterfaces\\PublicInterfaces;
Z:\\B16\\CATSmarTeamIntegInterfaces\\PublicInterfaces;
Z:\\B16\\CATSmInterfaces\\PublicInterfaces;
Z:\\B16\\CATTBDiagramInterfaces\\PublicInterfaces;
Z:\\B16\\CATTechOptimizerItf\\PublicInterfaces;
Z:\\B16\\CATToolingInterfaces\\PublicInterfaces;
Z:\\B16\\CATToolingServices\\PublicInterfaces;
Z:\\B16\\CATTPSInterfaces\\PublicInterfaces;
Z:\\B16\\CATTPSUIResources\\PublicInterfaces;
Z:\\B16\\CATTTRSInterfaces\\PublicInterfaces;
Z:\\B16\\CATTubingInterfaces\\PublicInterfaces;
Z:\\B16\\CATWGDiagramInterfaces\\PublicInterfaces;
Z:\\B16\\CATXCADServices\\PublicInterfaces;
Z:\\B16\\CATxPDMInterfaces\\PublicInterfaces;
Z:\\B16\\CDMAInteroperability\\PublicInterfaces;
Z:\\B16\\Communications\\PublicInterfaces;
Z:\\B16\\ComponentsCatalogsInterfaces\\PublicInterfaces;
Z:\\B16\\ConstraintModeler\\PublicInterfaces;
Z:\\B16\\ConstraintModelerInterfaces\\PublicInterfaces;
Z:\\B16\\CORBAServerInfra\\PublicInterfaces;
Z:\\B16\\DataExchangeBaseRepsItf\\PublicInterfaces;
Z:\\B16\\DataExchangeKernelItf\\PublicInterfaces;
Z:\\B16\\Dialog\\PublicInterfaces;
Z:\\B16\\DialogEngine\\PublicInterfaces;
Z:\\B16\\DMAPSInterfaces\\PublicInterfaces;
Z:\\B16\\DNBAsyActivityBase\\PublicInterfaces;
Z:\\B16\\DNBAsyActivityInterfaces\\PublicInterfaces;
Z:\\B16\\DNBBuild\\PublicInterfaces;
Z:\\B16\\DNBCollection\\PublicInterfaces;
Z:\\B16\\DNBD5IInterfaces\\PublicInterfaces;
Z:\\B16\\DNBDeviceInterfaces\\PublicInterfaces;
Z:\\B16\\DNBDeviceModel\\PublicInterfaces;
Z:\\B16\\DNBDpmInterfaces\\PublicInterfaces;
Z:\\B16\\DNBGraphEditor\\PublicInterfaces;
Z:\\B16\\DNBHumanModelingInterfaces\\PublicInterfaces;
Z:\\B16\\DNBIgpOlpUI\\PublicInterfaces;
Z:\\B16\\DNBIgpSetupInterfaces\\PublicInterfaces;
Z:\\B16\\DNBInfrastructure\\PublicInterfaces;
Z:\\B16\\DNBInspectInterfaces\\PublicInterfaces;
Z:\\B16\\DNBMath\\PublicInterfaces;
Z:\\B16\\DNBMHIInterfaces\\PublicInterfaces;
Z:\\B16\\DNBObjectModel\\PublicInterfaces;
Z:\\B16\\DNBReportingInterfaces\\PublicInterfaces;
Z:\\B16\\DNBResourceProgramInterfaces\\PublicInterfaces;
Z:\\B16\\DNBRobotBase\\PublicInterfaces;
Z:\\B16\\DNBRobotInterfaces\\PublicInterfaces;
Z:\\B16\\DNBRobotModel\\PublicInterfaces;
Z:\\B16\\DNBSimActivityInterfaces\\PublicInterfaces;
Z:\\B16\\DNBSimIOInterfaces\\PublicInterfaces;
Z:\\B16\\DNBSimulationBase\\PublicInterfaces;
Z:\\B16\\DNBSimulationCommands\\PublicInterfaces;
Z:\\B16\\DNBSimulationControl\\PublicInterfaces;
Z:\\B16\\DNBSimulationInterfaces\\PublicInterfaces;
Z:\\B16\\DNBSimulationLanguage\\PublicInterfaces;
Z:\\B16\\DNBSystem\\PublicInterfaces;
Z:\\B16\\DNBVNCInterfaces\\PublicInterfaces;
Z:\\B16\\DNBWorldModel\\PublicInterfaces;
Z:\\B16\\DNBWSQInterfaces\\PublicInterfaces;
Z:\\B16\\Drafting2DLInterfaces\\PublicInterfaces;
Z:\\B16\\DraftingInterfaces\\PublicInterfaces;
Z:\\B16\\ElecDeviceItf\\PublicInterfaces;
Z:\\B16\\ElecFlatteningItf\\PublicInterfaces;
Z:\\B16\\ElecFunctionalItf\\PublicInterfaces;
Z:\\B16\\ElecHarnessItf\\PublicInterfaces;
Z:\\B16\\ElecRoutingItf\\PublicInterfaces;
Z:\\B16\\ElecSchematicItf\\PublicInterfaces;
Z:\\B16\\ElectricalInterfaces\\PublicInterfaces;
Z:\\B16\\ENOVaultClientCPP\\PublicInterfaces;
Z:\\B16\\ENOVIAPlugIn\\PublicInterfaces;
Z:\\B16\\EnoviaV5Adapter\\PublicInterfaces;
Z:\\B16\\FileMenu\\PublicInterfaces;
Z:\\B16\\FittingInterfaces\\PublicInterfaces;
Z:\\B16\\FreeFormOperators\\PublicInterfaces;
Z:\\B16\\GenKnowledgeInterfaces\\PublicInterfaces;
Z:\\B16\\GeometricObjects\\PublicInterfaces;
Z:\\B16\\GeometricOperators\\PublicInterfaces;
Z:\\B16\\GSMInterfaces\\PublicInterfaces;
Z:\\B16\\GSOInterfaces\\PublicInterfaces;
Z:\\B16\\InfInterfaces\\PublicInterfaces;
Z:\\B16\\InteractiveInterfaces\\PublicInterfaces;
Z:\\B16\\KinematicsInterfaces\\PublicInterfaces;
Z:\\B16\\KnowHow\\PublicInterfaces;
Z:\\B16\\KnowledgeInterfaces\\PublicInterfaces;
Z:\\B16\\LatheMachiningInterfaces\\PublicInterfaces;
Z:\\B16\\ManufacturingInterfaces\\PublicInterfaces;
Z:\\B16\\Material\\PublicInterfaces;
Z:\\B16\\Mathematics\\PublicInterfaces;
Z:\\B16\\MeasureGeometryInterfaces\\PublicInterfaces;
Z:\\B16\\MechanicalCommands\\PublicInterfaces;
Z:\\B16\\MechanicalModeler\\PublicInterfaces;
Z:\\B16\\MechanicalModelerUI\\PublicInterfaces;
Z:\\B16\\MecModInterfaces\\PublicInterfaces;
Z:\\B16\\Navigator4DFormats\\PublicInterfaces;
Z:\\B16\\NavigatorInterfaces\\PublicInterfaces;
Z:\\B16\\NewTopologicalObjects\\PublicInterfaces;
Z:\\B16\\ObjectModelerBase\\PublicInterfaces;
Z:\\B16\\ObjectModelerSDM\\PublicInterfaces;
Z:\\B16\\ObjectSpecsModeler\\PublicInterfaces;
Z:\\B16\\OptimizationInterfaces\\PublicInterfaces;
Z:\\B16\\OSMInterfaces\\PublicInterfaces;
Z:\\B16\\PartDesignDataImport\\PublicInterfaces;
Z:\\B16\\PartInterfaces\\PublicInterfaces;
Z:\\B16\\PLMSecuritySSOBase\\PublicInterfaces;
Z:\\B16\\PPRInterfaces\\PublicInterfaces;
Z:\\B16\\Print\\PublicInterfaces;
Z:\\B16\\PrintBase\\PublicInterfaces;
Z:\\B16\\PrismaticMachiningInterfaces\\PublicInterfaces;
Z:\\B16\\ProcessPlatformBase\\PublicInterfaces;
Z:\\B16\\ProcessPlatformVisu\\PublicInterfaces;
Z:\\B16\\ProductStructure\\PublicInterfaces;
Z:\\B16\\ProductStructureInterfaces\\PublicInterfaces;
Z:\\B16\\ProductStructureUI\\PublicInterfaces;
Z:\\B16\\PSNInteroperability\\PublicInterfaces;
Z:\\B16\\SDMRuntime\\PublicInterfaces;
Z:\\B16\\SIMInterfaces\\PublicInterfaces;
Z:\\B16\\SIMPlayer\\PublicInterfaces;
Z:\\B16\\SIMSequenceModel\\PublicInterfaces;
Z:\\B16\\SimulationBaseLegacy\\PublicInterfaces;
Z:\\B16\\SimulationInterfaces\\PublicInterfaces;
Z:\\B16\\SketcherInterfaces\\PublicInterfaces;
Z:\\B16\\SketcherToolsUI\\PublicInterfaces;
Z:\\B16\\SketcherUI\\PublicInterfaces;
Z:\\B16\\SMTInterfaces\\PublicInterfaces;
Z:\\B16\\SpaceAnalysisInterfaces\\PublicInterfaces;
Z:\\B16\\SpecialAPI\\PublicInterfaces;
Z:\\B16\\StructureInterfaces\\PublicInterfaces;
Z:\\B16\\SurfaceMachiningInterfaces\\PublicInterfaces;
Z:\\B16\\System\\PublicInterfaces;
Z:\\B16\\Tessellation\\PublicInterfaces;
Z:\\B16\\ToolPathEditorInterfaces\\PublicInterfaces;
Z:\\B16\\TopologicalOperators\\PublicInterfaces;
Z:\\B16\\V5ToV4Geo\\PublicInterfaces;
Z:\\B16\\Visualization\\PublicInterfaces;
Z:\\B16\\VisualizationBase\\PublicInterfaces;
Z:\\B16\\VPMInterfaces\\PublicInterfaces;
Z:\\B16\\VPMServices\\PublicInterfaces;
Z:\\B16\\XMLParser\\PublicInterfaces;
Other Includes:
Stable Source Directories:
d:\\programme\\microsoft visual studio .net\\vc7\\atlmfc\\src\\mfc;
d:\\programme\\microsoft visual studio .net\\vc7\\atlmfc\\src\\atl;
d:\\programme\\microsoft visual studio .net\\vc7\\crt\\src;
|
| feline |
Posted - Jan 15 2008 : 09:23:44 AM
I don't know why this is not working for you. Can you please go to:
VA Options -> System Info -> Copy Info
and paste the details (from the clipboard) into this thread. This will give us the basic information about your setup. |
| andreas.theurer |
Posted - Jan 15 2008 : 03:30:30 AM
In opposite to the mistyped lines, spelling errors are underlined.
==> I tried your hint. I turned off both options and closed the options with ok. Afterwards I switched both on and closed the options with ok.
The mistyped line ( undeclared variable ) still isn't underlined.
Strange -> why does your VA, with the same version and the same IDEs version, behave in an other way than my VA, mmmhhhhh ??? |
| andreas.theurer |
Posted - Jan 15 2008 : 03:22:52 AM
Ok, I turned both options off. I closed the options menu with ok. Afterwards I turned them on again and closed the options with ok.
The mistyped line ( undeclared variables ) still isn't underlined.
-> Strange; why does your VA, with the same version and the same IDE-version, behave in an other way than my VA? |
| feline |
Posted - Jan 11 2008 : 11:29:02 AM
Are you seeing spelling errors in comments underlined by VA?
If you turn off both underlining spelling errors and mistyped symbols, accept this, and then turn them both on, does this make any difference?
I have just tested this here, and VA is underlining mistyped symbols for me in VS2002 with VA 1624. |
| andreas.theurer |
Posted - Jan 11 2008 : 02:58:15 AM
No I never see mistyped variables underlined by VA.
I use: VS C++ 2002 Version 7.0.9955
and: VA 10.4.1624.0 built 2007.12.07 |
| feline |
Posted - Jan 10 2008 : 1:54:28 PM
Do you ever see any mistyped variables underlined by VA? This is working for me.
Which IDE and version of VA are you using? |
| andreas.theurer |
Posted - Jan 10 2008 : 09:00:06 AM
This doesnG??t work. When the variables declaration is deleted, the variables should be underlined. Unfortunately it stays black and no underlining appears.
But I think I found another god working workaround to get the desired result.
I changed in the Visual Studio Options the color for the item G?IdentifierG? from black to red.
In the most cases it has exactly the desired result.
Sincerely Andy
|
| feline |
Posted - Jan 10 2008 : 08:38:21 AM
Try turning on:
VA Options -> Advanced -> Underlines -> Underline mistyped symbols using
and setting the underline to a nice distinct colour. Since the declaration has been removed the symbol should be underlined as a mistyped symbol. |
