I'm working on a Visual C++ project without MFC.
My project has different CPP files.
I use a self made DLL that contains classes.
Each CPP file includes a header file that describes a class that is implemented in the DLL.
Let's say I have File1.CPP and File2.cpp.
If I've created an instance of a class in File1.cpp, and I want to access a (public) memberfunction, I type:
and I automatically get a list of all the memberfunction and membervariables of this object.
If I do the same I File2.cpp I do not get that list of memberfunctions.
I think this has something to do with the "Source Browse Info File"
How come the behaviour of Visual C++ is different?
Can somebody tell me what I am doing wrong here?
Thanks in advance!
From what you've said it sounds like you're creating the instance in one source file and trying to access its member functions in another source file - which i think may be stretching the scope of its definition somewhat :)
I may be wrong...
No, you've got me wrong there.
In File1.CPP I use the class MyClass the following way:
And in File2.cpp I use the class MyClass too, just the same way:
It has nothing to do with scope problems, because then I would have compile errors.
I sometimes notice a different behaviour of Visual C++.
In File1.cpp I get the list of memberfunctions when I'm typing
the object's name (myObj1) and a point.
But in File2.cpp when I type the object's name and a point, Visual C++ does not show me the list of memberfunctions.
To be clear: my code compiles and links just fine.
Can you tell me how this is possible? (Visual C++ does not work the same way when I expect it to do)
If you're just including the headers for you dll's in your source files that use the functions they contain, the header files should be in the 'External Dependencies' folder in the Workspace window. If this is the case you can get the IntelliSense back by dragging these files (in the Workspace window) into the headers folder. Alternatively you could get Visual Assist, which improves the way that MSVC 6.0 does IntelliSense.