| Author |
 Topic  |
|
|
isbruch
New Member
Germany
4 Posts |
 Posted - Jan 17 2005 : 1:03:51 PM
|
I have regular .HPP include files which have, for a special reason, the extension .XPP.
I applied the suggestions made in the FAQ "How do I make Visual Assist X active on a file with a different extension?", but no syntax highlighting works. Also when I move the mouse over the symbol where it's used in a source file (a .cpp file) no information about the define, i.e. it's value, is displayed.
Any idea of what I do wrong?
Best regards,
KJ Isbruch
------------------------
I am using
VA_X.dll file version 10.1.1293.0
Licensed to:
VA X: [email protected] (6-user license) Support ends 2005.12.18
VAOpsWin.dll version 1.2.0.4
MSDev.exe version 6.0.8168.2
Devshl.dll version 6.0.8798.0
Devedit.pkg version 6.0.8447.0
Font: Courier -13(Pixels)
Comctl32.dll version 5.81.4916.400
WindowsNT 5.0 Build 2195 Service Pack 4
Single processor
Platform: Win32 (x86)
Stable Includes:
D:\\Program Files\\Microsoft Visual Studio\\VC98\\INCLUDE;
D:\\Program Files\\Microsoft Visual Studio\\VC98\\MFC\\INCLUDE;
D:\\Program Files\\Microsoft Visual Studio\\VC98\\ATL\\INCLUDE;
c:\\ProTopas\\include;
Library Includes:
D:\\Program Files\\Microsoft Visual Studio\\VC98\\MFC\\SRC;
D:\\Program Files\\Microsoft Visual Studio\\VC98\\MFC\\INCLUDE;
D:\\Program Files\\Microsoft Visual Studio\\VC98\\ATL\\INCLUDE;
D:\\Program Files\\Microsoft Visual Studio\\VC98\\CRT\\SRC;
Other Includes:
|
KJ Isbruch |
|
|
feline
Whole Tomato Software
United Kingdom
19021 Posts |
Posted - Jan 24 2005 : 3:19:23 PM
|
i have seen some problems with this feature, see 3394 for details. however i did get syntax highlighting to work.
are you sure you did all of the edits to the registry correctly? off hand i am not sure what else may have gone wrong. |
zen is the art of being at one with the two'ness |
 |
|
|
isbruch
New Member
Germany
4 Posts |
Posted - Jan 27 2005 : 07:39:24 AM
|
I think I found my problem. I downloaded the latest version of VA_X, uninstalled my current version, rebooted AND then deleted anything I could find about VA_X in the registry.
Then I installed the latest version of VA_X, applied the registry changes again (well, not the one for the developer studio, because I had that change already, before even knowing about VA_X) and now it works great.
Nevertheless, I appreciate your help and fast response.
|
KJ Isbruch |
|
|
| |
Topic |
|
|
|
Topic Locked
