| Author |
 Topic  |
|
|
selmo
Junior Member
19 Posts |
 Posted - Mar 10 2004 : 07:40:51 AM
|
Member variables in .inc files which are embedded in the class declaration aren't always recognized:
class foo
{
int private_local_var;
#include "my_common_class_members.inc"
};
Variables declared in the .inc file are recognized when opening the workspace, but become unrecognized (underlined) once I start editing a file which references them. Reparsing the file doesn't help, nor does either setting of the default intellisense option.
|
|
|
selmo
Junior Member
19 Posts |
Posted - Jun 10 2004 : 2:52:30 PM
|
| Just wondering if anyone is looking at this bug? There was no response to the original post. It's still happening in 1239 and I personally find it very annoying. After editing the file, member variables and functions are not recognized by intellisense at all if they are declared in an included non-header file within the class declaration. |
 |
|
|
support
Whole Tomato Software
5566 Posts |
|
|
selmo
Junior Member
19 Posts |
Posted - Jun 11 2004 : 2:52:33 PM
|
yes, that fixed it, thanks. I seem to remember having done that for my VA6 settings, but I guess I needed to do it for VAX as well. (setting didn't migrate)
|
|
|
|
selmo
Junior Member
19 Posts |
Posted - Apr 02 2005 : 02:49:17 AM
|
| Umm. This seems to have broken with 1299 with VC6. I've got the registry key set, and it was working dandy for a long time, but now it's not--nuthin declared in the inc is parsed or suggested by VA. Did the reg key change or location change? I see reg trees udner HKCU\\Software\\Whole Tomato for "Visual Assist" , "Visual Assist 6" and "Visual Assist X\\VA6"...and I've put the .inc in the ExtHeader key on all of them. Do I need to do something else here? |
|
|
|
selmo
Junior Member
19 Posts |
Posted - Apr 02 2005 : 03:09:47 AM
|
FYI:
VA_X.dll file version 10.1.1299.0
Licensed to:
VA X:
VA 6.0: [email protected] (1-user license)
VAOpsWin.dll version 1.2.0.4
MSDev.exe version 6.0.9782.2
Devshl.dll version 6.0.9782.0
Devedit.pkg version 6.0.9782.0
Font: Arial TUR 11(Pixels)
Comctl32.dll version 5.82.2800.1106
WindowsNT 5.1 Build 2600 Service Pack 1
2 processors
Platform: Win32 (x86)
Stable Includes:
C:\\Program Files\\Microsoft DirectX 9.0 SDK (February 2005)\\Include;
C:\\DXSDK\\Include;
C:\\Dev\\Microsoft Visual Studio\\VC98\\INCLUDE;
C:\\Dev\\Microsoft Visual Studio\\VC98\\MFC\\INCLUDE;
C:\\Dev\\Microsoft Visual Studio\\VC98\\ATL\\INCLUDE;
Library Includes:
C:\\Dev\\Microsoft Visual Studio\\VC98\\MFC\\SRC;
C:\\Dev\\Microsoft Visual Studio\\VC98\\MFC\\INCLUDE;
C:\\Dev\\Microsoft Visual Studio\\VC98\\ATL\\INCLUDE;
C:\\Dev\\Microsoft Visual Studio\\VC98\\CRT\\SRC;
Other Includes:
|
|
|
|
feline
Whole Tomato Software
United Kingdom
18941 Posts |
Posted - Apr 04 2005 : 3:32:25 PM
|
something odd is going on here. i can get VA 1297 to parse a C++ header with the extension "inl" but not one with the extension "inc"
do you know the last version of VA you used where this worked correctly? |
zen is the art of being at one with the two'ness |
|
|
|
selmo
Junior Member
19 Posts |
Posted - Apr 05 2005 : 04:41:52 AM
|
no, sorry, I'm not really sure which version last worked. It wasn't TOO long ago tho (not more than several months). It was working a year ago (see dates of prior posts in this thread) and it worked for months after that. So obviously somewhere between 1239 and 1299 it broke. (I know, not real specific)
I don't have the old versions of VA around to test it with. |
|
|
|
feline
Whole Tomato Software
United Kingdom
18941 Posts |
Posted - Apr 05 2005 : 4:11:58 PM
|
i don't seem to be getting anywhere here. i have also tried VA 1246 and i cannot get VA to parse *.inc files with this version either. i will put in a case and see what the developers make of it.
case=554 |
zen is the art of being at one with the two'ness |
|
|
|
selmo
Junior Member
19 Posts |
Posted - Apr 06 2005 : 05:23:57 AM
|
Just to be extra clear, VA never parses an included .inc file unless one adds .inc to the ExtHeader registry entry as described in the FAQ referenced above. (the default is ".h;.hh;.hpp;.hxx;.tlh;.inl;.p;" so .inl would be parsed without needing any registry changes) Adding .inc to that registry key did work with 1239 ten months ago.
WT seems to have moved and renamed the registry sections a few times, so the ExtHeader entry has moved as well... For example, I can find the ExtHeader key in no less than three separate registry heirachies now...which makes me wonder if the needed registry key is MIA or in the wrong place.
But alas... parsing of .inc files doesn't work AT ALL, no matter if I add .inc to ANY AND ALL of the ExtHeader registry keys in build 1299.
|
|
|
|
feline
Whole Tomato Software
United Kingdom
18941 Posts |
Posted - Apr 09 2005 : 4:43:53 PM
|
as a test i have installed VA 1239, and i cannot get it to suggest a class defined in a .inc file *sigh*
i appear to have the correct settings in the registry, and i have told VA to rebuild its symbol databases. hopefully we will get word from Support on this one sooner rather than later. |
zen is the art of being at one with the two'ness |
|
|
| |
Topic |
|
Topic Locked
