Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
User name:
Password:
Save Password
Forgot your password?

 All Forums
 Visual Assist
 Technical Support
 Problem with VA View
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

JohnCz
Junior Member

19 Posts

Posted - Aug 21 2012 :  9:58:32 PM  Show Profile  Reply with Quote
Since installation of the newest version of VA (VS: 2008, 2010, 2012) running on Windows 7.
In VS 2010, hovering over the class name brings up the class tree in VA View tab. Tooltip show correct path of the header file (VS 2010 include directory). However clicking on the function name brings implementation file from the VS 2012 directory.
For example: CMFCToolBarMenuButton.
Clicking on the class name opens C:\\Program Files (x86)\\Microsoft Visual Studio 10.0\\VC\\atlmfc\\include\\afxtoolbarmenubutton.h

Clicking on any function name opens file:
C:\\Program Files (x86)\\Microsoft Visual Studio 11.0\\VC\\atlmfc\\src\\mfc\\afxtoolbarmenubutton.cpp

The same behavior applies when "Open Corresponding File" button is used:
If Clicking on the class name opens C:\\Program Files (x86)\\Microsoft Visual Studio 10.0\\VC\\atlmfc\\include\\afxtoolbarmenubutton.h is active, clicking on the button opens C:\\Program Files (x86)\\Microsoft Visual Studio 11.0\\VC\\atlmfc\\src\\mfc\\afxtoolbarmenubutton.cpp

Clicking on the button when C:\\Program Files (x86)\\Microsoft Visual Studio 11.0\\VC\\atlmfc\\src\\mfc\\afxtoolbarmenubutton.cpp is active brings Clicking on the class name opens C:\\Program Files (x86)\\Microsoft Visual Studio 10.0\\VC\\atlmfc\\include\\afxtoolbarmenubutton.h

Therefore, there is obviously some problem with recognizing location of the header and implementation files.

In VS 2008 clicking on the member function, always opens a header file, not implementation file. "Open Corresponding File" button works as expected.

-------------------------------------------------
VA_X.dll file version 10.7.1912.0 built 2012.08.08
Licensed to:
VA X: ... Support ends 2013.04.01
DevEnv.exe version 10.0.40219.1 Ultimate
msenv.dll version 10.0.40219.1
Comctl32.dll version 6.10.7601.17514
Windows 7 6.1 Build 7601 Service Pack 1
4 processors (x86-64;
WOW64)
Language info: 1252, 0x409

Platform: Project defined
Stable Includes:
C:\\Program Files (x86)\\Microsoft SDKs\\Windows\\v7.0A\\include;
C:\\Program Files (x86)\\Microsoft Visual Studio 10.0\\VC\\atlmfc\\include;
C:\\Program Files (x86)\\Microsoft Visual Studio 10.0\\VC\\include;

Other Includes:

Stable Source Directories:
C:\\Program Files (x86)\\Microsoft Visual Studio 10.0\\VC\\crt\\src;
C:\\Program Files (x86)\\Microsoft Visual Studio 10.0\\VC\\atlmfc\\src\\atl;
C:\\Program Files (x86)\\Microsoft Visual Studio 10.0\\VC\\atlmfc\\src\\mfcm;
C:\\Program Files (x86)\\Microsoft Visual Studio 10.0\\VC\\atlmfc\\src\\mfc;

feline
Whole Tomato Software

United Kingdom
19148 Posts

Posted - Aug 24 2012 :  11:24:23 AM  Show Profile  Reply with Quote
Are you using the RTM VS2012, or the release candidate?

Are you able to reproduce this problem in a new, default solution? So far I cannot reproduce this problem here, testing VS2010, VA 1912 with VS2012 RTM installed along side, running under Windows 7 64bit.

zen is the art of being at one with the two'ness
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000