This one drives me up the walls... I frequently use the "Called by"-feature, available from the drop down occuring when right-clicking a function symbol in the Class View. Now, for no apparent reason, this has stopped working! I have tried deleting all of the files in the Debug-folder, deleting the ncb file, checking that the Build Browse Info box is checked in the project settings and then re-compiling. All to no avail. Selecting "Called by" for any function renders... nothing. Not even an error message! Any clues, people! Thanx in advance for any tips on this one! ------------------------------------------------------------ "Pooollyyy!! ...Polly Parrot! Wakey-wakey!"

Less than a minute after posting my question I googled out the following page: http://www.perforce.com/perforce/doc.031/manuals/p4plugins/02\_visualcpp.html Scroll down to the second last heading; "which files do I put in the depot?". Any additional thoughts and input on the subject from You guys out there are still much appreciated! ------------------------------------------------------------ "Pooollyyy!! ...Polly Parrot! Wakey-wakey!"

Hi all! Setting up a multi-developer Visual C++ project, which non-code files (i.e. not h- or cpp-files) would You include for source control? Obviously, all h- and cpp-files dhould be included, but then what? There has been some debate going on at the office on whether for instance the dsp and dsw files should be configured. A concrete example: we have suffered problems with what files/classes show up in a clients view after a sync to head following the check-in of new files/classes by another developer. By the way, we are using Perforce. Your input will be much appreciated! ------------------------------------------------------------ "Pooollyyy!! ...Polly Parrot! Wakey-wakey!"

I have this class declared as ------------------------------------------------------------------- class CMyArray : public CTypedPtrArray< CObArray, CMyDataClass* > { public: ... CMyArray(); virtual ~CMyArray(); protected: ... }; ------------------------------------------------------------------- where the CMyDataClass is declared as ------------------------------------------------------------------- class CMyDataClass:public CObject { public: CMyDataClass( ); virtual ~CMyDataClass( ); ... protected: ... }; ------------------------------------------------------------------- Upon compile I get this error: error C2653: 'CMyArray' : is not a class or namespace name What?! The strangest thing is that I have other classes defined in the exact same way, compiling without problems. I searched the documentation using the error code for keyword and found some vague references to this being a known bug, but I could not work out a solution from the text. Obviously, I am doing something wrong with the CMyDataClass, since I do get the exact same construction to work with other generic classes. ------------------------------------------------------------ "Pooollyyy!! ...Polly Parrot! Wakey-wakey!"

UHh... OK. I thought that the "= not defined" thing was about CMap member functions not being able to compare keys rather than the objects...? Anyway, thanks I'll try that! ------------------------------------ Håkan Olsson, M. Sc. Technical Project Manager Airborne Hydrography AB, Sweden http://www.airbornehydro.com NOTE: All standpoints, opinions, suggestions etc in the above stands for me and me alone and are not in any way affiliated with or endorsed by Airborne Hydrography AB.

Hi everybody, here's a newbie one for y'all: I was hoping that I'd be able to create an instance of CMap using very simplistic keys with something like: CMap< int, int&, CMyClass, CMyClass& > m_myMap; But I get a "'operator =' function is unavailable" error from the compiler. Is this because I have to use keys that are objects of a class, or what? Best regards, Håkan Olsson ------------------------------------ Håkan Olsson, M. Sc. Technical Project Manager Airborne Hydrography AB, Sweden http://www.airbornehydro.com NOTE: All standpoints, opinions, suggestions etc in the above stands for me and me alone and are not in any way affiliated with or endorsed by Airborne Hydrography AB.