| T O P I C R E V I E W |
| peterboulton |
Posted - May 17 2006 : 08:31:01 AM
Hi,
I'm evaluating Visual Assist X at present and absolutely love it!
Just one annoyance really - if I choose a (C++) member function in the 'Symbols in Workspace' dropdown of VA View I seem to go to the declaration (the .h file) rather than the definition (the .cpp file).
Is this intentional / desirable? I would definitely prefer to go to the definition (the .cpp file). Is it possible to make Visual Assist X always do this by default?
Thanks!
Pete |
| 7 L A T E S T R E P L I E S (Newest First) |
| peterboulton |
Posted - May 18 2006 : 09:56:01 AM
Thanks! I didn't know what FSIW stood for but I appear to have been enjoying using it! :->> |
| support |
Posted - May 18 2006 : 09:40:45 AM
http://www.wholetomato.com/products/features/siw.html?more=yes |
| rhummer |
Posted - May 18 2006 : 09:02:47 AM
FSIW = Find Symbols In Work Spac
the free trial doesn't hide any features ;)
All the terms are explained in the documentation on the site, I'd suggest you read through it. you will find alot of new things you probably didn't know about ;) |
| peterboulton |
Posted - May 18 2006 : 03:36:49 AM
Thanks feline. I think I can manage Alt+G!
(Not sure what "FSIW" stands for - perhaps this is only a feature for registered users! :->> Which I soon will be - Visual Assist is a terrific productivity aid and I love it to bits!)
|
| feline |
Posted - May 17 2006 : 4:38:06 PM
first the easy work around, when you are taken to the header press alt-g without moving the caret, you should be taken to the function body. this is also useful when using alt-g to find the function in the first place.
doing a quick test with VS2005, it seems that FSIW now goes to the body rather than the header by default in the 15xx builds. these are currently being developed and beta tested, and should go on general beta "soon". |
| peterboulton |
Posted - May 17 2006 : 11:31:42 AM
Sorry, I should have said! 
I'm using Visual Studio 2005 and Visual Assist X build 10.2.1445.0 built 2006.04.12.
The other (hopefully relevant) stuff is:
VAOpsWin.dll version 1.3.2.4
VATE.dll version 1.0.4.15
DevEnv.exe version 8.0.50727.42
msenv.dll version 8.0.50727.42
Comctl32.dll version 6.0.2900.2180
WindowsNT 5.1 Build 2600 Service Pack 2
Single processor
Platform: Win32
I'm really sorry about forgetting that info in my original question, and thanks for taking the trouble to respond.
Pete |
| rhummer |
Posted - May 17 2006 : 11:19:10 AM
Are you using the latest release 1445, and what IDE ?
I am currently using a few beta builds, which I am seeing the behaviour you desire. So its possible it has been changed. I would give it a try when the beta builds go public.
feline, support can you confrim? |
