I upgraded from VA_X_Setup1246.exe to VA_X_Setup1289.exe and I'm developing with VS.Net 2003 using C++.
I've found that the "Goto Implementation" feature doesn't work as well as it used to. I often find myself clicking on the button without seeing any results whatsoever. I just don't remember it being so unreliable in the past, but it's still far better than the implementation that Microsoft uses which doesn't ever seem to work.
As a suggestion I think it would be nice if the "Goto Implementation" could tell the difference between a forward definition and a true definition of a class. I will often declare a class in a headerfile like this:
class MyClass;
The "Goto Implementation" feature usually finds them and lists them instead of finding the place where the class is actually defined.
I see the bug quite often so I'm not sure where the file name relates to the file that's currently open. I haven't read your link, but from a user's point of view if the compliler can find the file then so should VA. Can't you just open up the set file and look through all the paths until you find the file? I've given up hope in Microsoft ever implementing this feature properly but your software is so close to doing it right that I know you could get it. If you could rollback the functionality to what was in the software just a few versions ago the feature will work much better.
VA_X.dll file version 10.1.1418.0 built 2005.06.24 Licensed to: VA X: [email protected] (7-user license) Support ends 2006.02.28 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: Courier -13(Pixels) Comctl32.dll version 5.82.2900.2180 WindowsNT 5.1 Build 2600 Service Pack 2 Single processor
I am having similar problems. I noticed that the the goto definition field is empty when I click on a class (ex. class TVector) that is included as follows:
#include "geo/TVector.h"
If I move the file from the folder geo/ to its subfolder, then everthing is ok.
I hope this help in finding the problem. If you have a suggestion that will avoid this problem, then I surely would like to hear about it.
The parent folder of ./geo/ is not present in the VC6 environment additional include directories. However, the parent foler is present in the DSP project additional include directories. For many reason (which I won't get into right now) I cannot added to the VC6 environment additional include directories.
NOTE: This was working fine before I updated to VA_X_Setup1418.exe. I Was using VA_X_Setup1297.exe in the past.
case=689 vc6 project additionalIncludeDirectories not extracted
This will be fixed in the next build.
In the meantime, I believe a workaround is to add the parent folder to the VA "Other include files" list on the C/C++ Directories node of options dialog (you will have to change the VA platform from Win32 to Custom).
Topic Locked
Posted - Jan 28 2005 : 11:25:12 PM
