| T O P I C R E V I E W |
| Paul Eisenbrey |
Posted - Oct 11 2007 : 4:28:36 PM
To start with, I've been a fan of Visual Assist since I started using it on Visual Studio 5. But I must say this most recent iteration has been far to buggy. I have several issues, some of which I've seen on other posts, and some appear to be unique. The biggest problem I have, and the reason I haven't posted before, is I cannot reliably reproduce any of these issues. They appear to occur without rhyme or reason.
My system:
Vista Business, all updates.
Intel quad core.
4GB ram,
Visual Studio 2005
BIG project: around 200 files and 800,000 lines of code.
VA version 10.4.1609.0
Here are my issues:
1) When I've selected Local Symbols in Bold, and Stable Symbols in italics, Occasional lines of code are garbled. Sometimes the characters are literally garbage, and sometimes it is just shows the wrong code. When I highlight the garbage line, the correct text appears. Of course, I cannot work on a file where all the text is highlighted, so I keep the Bold and Italic options off. This may or may not have been fixed in the last iteration, but I've not seen problem this discussed on this board.
2) Every so often, the PgUp key won't function. Disabling VA re-enables it, and re-enabling VA disables it. Th only cure is to close all documents and re-open the one I'd been editing. Leave even one up and the behavior persists.
3) Occasionally, left paren won't print. This is not the defect I've seen on this board, where the paren is going to the wrong window -- where "Show Miscellaneous files in Solution Explorer" in Tools|Options|Environment|Documents." is on. It isn't.
4) GoTo definition fails quite often. Sometimes it takes me to the top of the correct file, but fails to position the cursor on the right line. Sometimes it just beeps.
As an aside -- I don't know if it is relevant, but I run Visual Studio spread across two monitors, where the primary monitor has the Output Window, Code Definition Window and Solution Explorer. The secondary monitor is where I have my edit windows.
--Paul Eisenbrey |
| 11 L A T E S T R E P L I E S (Newest First) |
| sean |
Posted - Oct 17 2007 : 10:55:09 PM
Let's continue this by email.
Please use this form and simply reference "topic=6806 for sean" in the message
http://www.wholetomato.com/support/contact.asp
|
| Paul Eisenbrey |
Posted - Oct 17 2007 : 5:53:57 PM
If the file has been opened and closed, alt-g works fine. It appears to occur only when the file has not been opened during that session.
It occurs regardless of the number of open files -- It'll do it when I only have one up. But to answer your question, I generally have between 5 and 25 files open at a time.
The control in the VA view sees the function just fine, along with the function header comments. But clicking on the func name in the tree produces the same results as alt-g. |
| sean |
Posted - Oct 17 2007 : 5:28:45 PM
quote:
Originally posted by Paul Eisenbrey
In the first Alt-G scenario, this is usually local project files. At the moment, it is very regular. If the file has not been opened during the session, alt-g goes to the top of the file containing the definition. Once the file has been opened, alt-g works correctly.
Does it work correctly if the file has been opened and then closed, or does it only work while the target is still open? This is sounding like a problem with general file navigation rather than a problem with the symbol database - which would explain why a rebuild has no effect.
How many source windows do you typically have open? Any correlation between the number of open windows and when problems arise?
In the Va View tool window is the HCB tree control. If you hover over one of the symbols that alt+g doesn't work properly for, does the HCB update showing the symbol? If so, does double-click on the item work properly?
|
| accord |
Posted - Oct 17 2007 : 3:31:06 PM
Sean: http://forum.wholetomato.com/forum/topic.asp?whichpage=1&TOPIC_ID=6762#27217 |
| Paul Eisenbrey |
Posted - Oct 17 2007 : 1:39:27 PM
Okay. I'm back to version 1561 -- the uninstall advice did not work for me. I don't recommend it for anyone else, either.
In the first Alt-G scenario, this is usually local project files. At the moment, it is very regular. If the file has not been opened during the session, alt-g goes to the top of the file containing the definition. Once the file has been opened, alt-g works correctly.
When going from a local source file to an MFC file -- like afxmsg.h -- I also end up at the top of afxmsg. Subsequent alt-g's to that file work correctly.
As for the second alt-g scenario, the MFC directories are present in the path dialogs. This error occurs less frequently, and I do not have a reliable set of repro steps for it. But it usually occurs from one system file to another, rather than within project files.
Finally, rebuilding the dataset has no effect on the defect. |
| sean |
Posted - Oct 16 2007 : 9:53:51 PM
accord: what problems are you experiencing that require a manual reinstall? If they are related to symbols/parsing then a symbol database Rebuild (VA Options | Performance | Rebuild ) would less intrusive than a reinstall.
Paul: For the first alt+g failure mode, are these files:
'system' files (like mfc or crt source)
files in your own solution
non-system files that are not in your solution
For the second alt+g failure mode: Do you have the mfc directories listed in the IDE options at:
Tools|Options|Projects and Solutions|VC++ Directories| Show Directories for Source files ?
If so, do they also appear in the VA Options dlg at:
VAssistX|Visual Assist X Options|Projects|C/C++ Directories| Show Directories for Source files ?
The VA source file list will automatically mirror the IDE source file list unless you have chosen a custom platform in the VA options dlg.
Do you experience these problems after a symbol database rebuild (VA Options|Performance|Rebuild button) ?
|
| accord |
Posted - Oct 15 2007 : 7:04:43 PM
Have you tried uninstalling, and then re-installing VAX?
Maybe won't work for you, but last time I had similar problems (alt+g failure, or jumps to the top of the file first, and working for the second time, etc.) I reinstalled VAX and it seems to be working now.
Normally I am installing new versions without uninstall, but in very rare conditions, a manual re-install is required to fix problems.
|
| Paul Eisenbrey |
Posted - Oct 15 2007 : 11:09:35 AM
(4) GoTo problems.
I've been playing with this the past couple of days, and have some new information. There are two distinct failure modes. First, when VA takes me to the top of the correct file, but not to the right line number. This tends to happen when the file I'm being shuttled to is not open. Interestingly, if I repeat the steps after the file is open VA takes me to the correct line. It continues to behave correctly even after I've closed the file. So, it appears to hinge on whether the destination file has ever been opened. If the file has not, I can get the error. If it has, things work.
The second failure is when <Alt>-G just produces a ding sound. I got it to repro this morning by trying to go from an MFC source file to another microsoft source file. I was in cstring.h, set the cursor on an instance of the ReleaseBufferSetLength() function, and pressed <Alt>-G. ding. The function is defined in atlsimpstr.h, and the definition shows in the Code Definition Window, so I know there is a legal linkage to it in the code. This behavior does not change, even if the source file is open.
VA's code definition drop down doesn't appear to know about the symbol, though. All that shows there is the path to the current file.
I hope that helps.
--Paul |
| sean |
Posted - Oct 13 2007 : 3:16:01 PM
Let's focus on item 4 first.
Does it fail consistently only on certain symbols?
or does it wok consistently and then start to fail over time?
or is it a more general failure?
|
| Paul Eisenbrey |
Posted - Oct 12 2007 : 1:13:33 PM
True, I'm using the beta -- I saw a link to it on another topic. But these effects have occurred in every version since I purchased VAX last spring.
1) The font is Courier New (10). I don't know if changing the font will fix it, as I've been running with the bold and italic options off for the last few iterations. I've just turned the bold and italic options back on, and I'll re-post if the error resurfaces.
2) No other packages.
3) Gad zooks I'm glad to hear that. It's been driving me insane.
4) Yes. I turned it on sometime last summer, because I thought perhaps the VAX dataset was getting confused. It doesn't seem to make a difference, though.
Lest this gets too negative, I'd like to add that, for the most part, VAX has been nothing less than terrific. It is a huge productivity boost in its current configuration. And once these last few issues have been worked out it'll be even better.
--Paul Eisenbrey |
| sean |
Posted - Oct 11 2007 : 9:00:03 PM
Thanks for the comments. Build 1609 is not available on our downloads page. It is a beta build that has only been announced in the public beta forums. Were you directed to it through support or did you download it after reading the beta announcement? (The reason I ask is that you have posted these comments in the General Release group rather than the Public Beta group - so it is not clear that you know it is a beta release)
Issues:
1. Is this problem font dependent? Do you experience similar problems if you use a different font? What font are you using? Was this a problem in any previous versions of VA?
2. Do you have any other addins/packages installed? Was this a problem in any previous versions of VA?
3. This has been difficult for us to reproduce, but we do expect that it will be fixed in build 1612.
4. Do you have the VA "Parse all files when opening a project" option enabled (VA Options|Performance)?
|
|
|
