| T O P I C R E V I E W |
| Moby Disk |
Posted - Mar 19 2009 : 08:08:25 AM
I have a bunch of directories with source code that is not associated with a Visual Studio project file. I just use it as an editor. Although highlighting works, "Go To Definition" does not work. The toolbars and VA Outline work though. Is the "Go To Definition" provided by Visual Studio or VAX?
I'd especially like to use VAX to "Go to definition" to other .h and .cpp files in the directory. Should this work? OR do I just need to make a Visual Studio project file, and put my code into it, and just not use the compiler? |
| 3 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Mar 20 2009 : 11:40:45 AM
This is unlikely to happen any time soon. One reason is that sometimes the IDE's Go to declaration command does something more useful than VA's alt-g.
This page might be of interest:
http://www.wholetomato.com/products/features/goto.asp |
| Moby Disk |
Posted - Mar 19 2009 : 7:54:09 PM
alt-g! Yeeha!
Can you change it so that the menu option is replaced with that? |
| feline |
Posted - Mar 19 2009 : 10:23:46 AM
In part it depends on the version of VA you are using. From the history of changes page, VA 1707 added:
* New! Added support for makefile projects (e.g. solutions without files) by parsing the physical directory tree of files as they are opened. (case=18918)
so if you are using VA 1707 or a newer build then VA should be parsing the files in the same directory as the open files.
If you are using an older version then making a project file and adding your files, and simply ignoring the compiler is a good, and hopefully fairly simple solution.
If you right click on a symbol and select "Go To Definition" or "Go To Declaration" then you are triggering IDE commands. Use Alt-g instead to trigger the VA command. |
