| T O P I C R E V I E W |
| hensz |
Posted - Apr 30 2007 : 07:00:20 AM
Hi!
I'm using build 1553 of VisualAssist X. I've used several version before, and since the last two or three versions IntelliSense and Suggestions don't work correct at some times.
I created a new project in VS 2005 (MFC Application, Dialog-based), added #include<string> and created a std::string object in the InitInstance method of my application class. When I want to call any member of string the list of members is totally wrong:
Next, I created a CString object. In the next line I wanted to use this object, but the Suggestion list didn't contain the newly created object. This happens all the time is is very annoying:
And finally, basic IntelliSense functionality is not working all the time. I wanted to call a method of my CString object, but the funcion definition is not shown. With deactivated VA it looks like this:
and with activated VA it looks like this (I pressed Ctrl+Shift+Space several times!):
It would be great if this problems could be solved. Now working with VA is just like working without it, or even worse. Sometimes VA replaces the correct code I've written with some garbage due to this problem.
Best regards,
Hensz |
| 4 L A T E S T R E P L I E S (Newest First) |
| hensz |
Posted - May 06 2007 : 06:23:19 AM
quote:
Ideally we would like to find out what causes the symbol database to become corrupt, so we could stop this happening, but this is easier said than done.
That's the point. I cannot tell when exactly when VA started to behave strange, so I cannot understand the reason why this happend. Perhaps it was a Windows Update, perhaps a crash...
Anyway, thanks for the quick solution. It's working for now, so I'm happy.
Best regards,
Hensz |
| feline |
Posted - May 02 2007 : 11:06:02 AM
It is worth a try. It depends on what sort of problems you are seeing, but if "everything goes wrong" it is a good place to start. Ideally we would like to find out what causes the symbol database to become corrupt, so we could stop this happening, but this is easier said than done. |
| hensz |
Posted - May 02 2007 : 07:14:34 AM
Ok, installing the new version solved all stated problems. 
So when VisualAssist behaves strange rebuilding the symbol database could help? |
| feline |
Posted - Apr 30 2007 : 11:17:16 AM
Clearly this is not good. I have just tried a couple of these tests using VS2005 and VA 1555 and I am not seeing any problems.
VA is suggesting "strTest" just after I have created it, and I am getting the correct parameter tooltip for Trim().
Looking at your screen shot I am noticing that "Trim" is underlined as a mistyped symbol, which will be why you are not getting any parameter information.
Can you please try upgrading to VA 1555 to see if this makes any difference:
http://www.wholetomato.com/downloads/getBuild.asp?1555
The upgrade will trigger a rebuild of your symbol database, which is probably a good thing given these problems. |
|
|
