• At the end of functions when I hit 'r' to type 'return', in VS2005 this would always be the first item on the suggestion list since I do that quite a lot and it's a very natural thing to do just before the closing bracket in a function. Now, however, many other symbols like RET_SOME_CONSTANT are suddenly also on the list, sometimes taking precedence over the one I want (return). This is often very annoying, since I'm quite used to just typing the first letter and hitting Enter since I know that's what VAX would suggest (and thus it speeds up my coding tremendously)


• There seems to be some major issues with the STL library in the latest version of VAX. Take for-loops, for instance, in which I want to access .begin() and .end() of, say, a simple std::vector. VAX is now often unable to suggest the right method and if I hit begin( it writes BEGIN_ATTRCOM_MAP instead. If I erase the suggestion by ctrl+z (as I always did in VS2005 when VAX would suggest something wrong) and try typing begin( again, VAX once again inserts BEGIN_ATTRCOM_MAP rather than letting me write what I want (this happens for other custom classes too that VAX for some reason is unable to parse). I just rebuilt the symbol database and VAX still isn't able to recognize a simple 'const vector<unsigned long>& someVar' function argument.


• VAX has auto-correction of variable names (to fix incorrect capitalization etc.). The problem I'm experiencing now is that if VAX is unable to parse the objects (which currently happens way too often) it incorrectly corrects the variable name when I hit . and it doesn't matter if I hit ctrl+z to undo the changes. That is, when I hit . VAX changes the variable name to a symbol it knows and I can't avoid VAX auto-correcting the variable name.


• VAX has also shown to have problems parsing virtual base classes. Soetimes, it cannot provide function information for pure virtual classes.


• When creating a new class and I want to write 'private", I start by typing 'pri' and VAX suggests the following: PRI_KEY_FLAG, prime_field, PrimeAndGenerator, and PRIVATE before finally listing the entry I want (private). The aforementioned constants are all part of the Crypto++ library, which I guess the latest version of VAX is now parsing correctly (at least I didn't see these constants interfering with my coding in older versions of VAX). It's clear that the constants are listed in alphabetical order, but they should really fit into the context as well. If I'm defining a class, chances are that I'm looking for 'private', 'protected' and 'public' rather than a random constant in a third-party library like PRIVATE. The same goes for writing parameters to a function call. VAX now suggests class and struct names rather then local variables. For instance, if I have a struct called Game and a local variable called 'game', VAX suggests Game before 'game'. VAX used to handle this better. Furthermore, it feels like all my own symbols are always listed last, rather than first, even though there's a higher chance I want to use my own than a third-party's.


• Often, in VS2008, VAX suddenly starts parsing a file and while it's doing so I'm unable to use Alt+G. For instance, if I go to a source file and change a method in a class, VAX reparses the file but does it so slowly that using the excellent Alt+G shortcut doesn't work even 5 seconds after I made the change (which means I have to fall back on Visual Studio's IntelliSense)

#include <vector>

static void testStdVectorFunctions(const vector<unsigned long>& someVar)
{
	someVar|;
}

quote:

---

Originally posted by feline

For now though this should help while we work on the bigger problems first.

Point 2, do you have the time to run a couple of quick tests please? Can you add the following code to one of your cpp files:

#include <vector>

static void testStdVectorFunctions(const vector<unsigned long>& someVar)
{
	someVar|;
}

when I do this, and then type ".beg" VA is correctly listing "begin" in the listbox.
With ".be" I am seeing the two items "begin" and "rbegin"

---

• Some files (the fairly simple and small ones) seem to work just fine for e.g. STL vectors


• In larger files (e.g. ~1000 lines), when I click . VAX indicates that it's parsing the file but nothing happens. If I click somewhere else and then go straight back to the original location and hit . again, VAX indicates it is parsing again. It feels like it fails to parse the file. The parsing message is also displayed for several seconds in the VS status bar although the CPU usage continues to stay low. Sometimes, if I wait patiently for the parsing to finish, delete the ., and hit . again then I can get the methods on the vector. However, if I then erase the . and hit . again, VAX tries to parse the file once again

#include <vector>

static void testOnlyVectorFunction(vector<unsigned long> paramVecOnly)
{
	paramVecOnly|;
}

static void testStdVectorFunction(std::vector<unsigned long> paramStdVec)
{
	paramStdVec|;
}

#define START_NAMESPACE namespace Uniwares {
#define END_NAMESPACE };

quote:

---

Originally posted by feline

#define START_NAMESPACE namespace Uniwares {
#define END_NAMESPACE };

and these are causing some problems in VA 1624. dreijer and Rain Dog do your projects contain anything similar?

---

quote:

---

Originally posted by feline

Something seems seriously broken for quite a few people in 1624, but what is it?

---

#include <vector>

static void testOnlyVectorFunction(vector<unsigned long> paramVecOnly)
{
	paramVecOnly;
}

static void testStdVectorFunction(std::vector<unsigned long> paramStdVec)
{
	paramStdVec;
}

quote:

---

Originally posted by feline

This at least I can explain. Consider this line of code:

int nFoo|

what is the variable name? Is the variable "nFoo" or am I actually half way through typing "nFooBar"? VA will not attempt to make "nFoo" bold until it is sure this is actually a variable name. Typing a dot after it will make this clear, since that ends the variable name and starts something else.

Does this make sense?

---

quote:

---

Originally posted by feline

If you show VA View, then place keyboard focus back into the editor, and now hover the mouse over one of these variables is the correct information displayed?

---

quote:

---

Originally posted by feline

This delay sounds like it should mean something, but I am not sure it is helpful.

---

quote:

---

Originally posted by feline

Lets try going back to basics. Do you have a file and a variable where typing dot never produces the correct listbox?

---

quote:

---

Originally posted by feline

Do you have:

VA Options -> Advanced -> Listboxes -> Get content from default Intellisense

turned On or Off? Does playing with this setting make any difference?

---

• Auto-completion suggestions are now very slow. Often, I can write almost the entire variable name before the suggestion list box pops up (and sometimes it doesn't even show).
• Hitting Enter once I've selected the symbol in the list box (like end()) doesn't automatically insert the brackets as VAX usually does.

quote:

---

Originally posted by feline

Just to double check, you are seeing the same problem when you delete most / all of the code in one of the files in your main solution?

---

>	ntdll.dll!76e22ea8() 	
 	[Frames below may be incorrect and/or missing, no symbols loaded for ntdll.dll]	
 	ntdll.dll!76e76394() 	
 	ntdll.dll!76e8f158() 	
 	ntdll.dll!76e8f1de() 	
 	ntdll.dll!76de8dd4() 	
 	ntdll.dll!76de40f0() 	
 	ntdll.dll!76e41039() 	
 	ntdll.dll!76e4100b() 	
 	ntdll.dll!76e029d7() 	
 	ntdll.dll!76e40e97() 	
 	ntdll.dll!76e41843() 	
 	ntdll.dll!76e416dc() 	
 	ntdll.dll!76e41843() 	
 	user32.dll!769f1a91() 	
 	user32.dll!769f1b41() 	
 	VA_X.dll!1eefbf13() 	
 	VA_X.dll!1eec4ef8() 	
 	VA_X.dll!1ee3ca90() 	
 	VA_X.dll!1ee3d971() 	
 	VA_X.dll!1ed281b3() 	
 	VA_X.dll!1ed9b2a7() 	
 	VA_X.dll!1ed1669a() 	
 	VA_X.dll!1eefbf13() 	
 	VA_X.dll!1ed02ab4() 	
 	VA_X.dll!1ed02afa() 	
 	VA_X.dll!1eef794a() 	
 	VA_X.dll!1eef796e() 	
 	VA_X.dll!1eecbee2() 	
 	VA_X.dll!1eec77c2() 	
 	VA_X.dll!1edccd7c() 	
 	VA_X.dll!1eeca0ac() 	
 	VA_X.dll!1eeca139() 	
 	user32.dll!769f1a10() 	
 	user32.dll!769f1ae8() 	
 	user32.dll!769f1a91() 	
 	user32.dll!769f2a47() 	
 	user32.dll!769f2a98() 	
 	VA_X.dll!1ed28a96() 	
 	msenv.dll!5bca5b21() 	
 	msenv.dll!5bca5abc() 	
 	msenv.dll!5bca5a8b() 	
 	msenv.dll!5bc9f99e() 	
 	msenv.dll!5bca3b2d() 	
 	devenv.exe!2f3ea4a6() 	
 	devenv.exe!2f3e7301() 	
 	ntdll.dll!76e40000() 	
 	ntdll.dll!76e42447() 	
 	ntdll.dll!76e41843() 	
 	ntdll.dll!76e45244() 	
 	ntdll.dll!76e45244() 	
 	advapi32.dll!76ab60ce() 	
 	advapi32.dll!76ab610c() 	
 	advapi32.dll!76ab663c() 	
 	ntdll.dll!76e3f360() 	
 	advapi32.dll!76ab649d() 	
 	advapi32.dll!76ab6578() 	
 	advapi32.dll!76ab6578() 	
 	devenv.exe!2f3e1d09() 	
 	kernel32.dll!75783833() 	
 	ntdll.dll!76e1a9bd()

#include <vector>
using std::vector;

void func()
{
	vector<Map> ding;
	for (vector<Map>::const_iterator dingItor = ding.begin)
	{
	}
}

quote:

---

Originally posted by feline

How large is your solution? If you open the OFIS and FSIS dialogs the title bars tell you the total number of symbols. What are these numbers?

---

quote:

---

Originally posted by feline

What is the memory usage for the IDE?

---

quote:

---

Originally posted by feline

Do you have:

VA Options -> Performance -> Keep symbols in memory for fast response after Alt+Tab

turned on or off?

---

• Sometimes when entering {, a closing } was not automatically inserted. This behavior was very inconsistent. Sometimes VAX inserted the closing bracket, other times not.
• Most of the overridden functions basically just needed to call a method on a private member variable. However, often I would write the variable name and hit -> without any effect. Then I would have to wait for VAX to recognize the symbol. Once the symbol had been found, the list box with methods appeared instantly. However, once I selected a method and I began typing the arguments, which happened to match the arguments to the method I had overridden, I would often experience that VAX wasn't able to help me auto-complete it. I would type almost the entire word before VAX would recognize it. Sometimes, I could almost finish typing all the arguments for the function before VAX started recognizing any of them. I never experienced any serious spikes in CPU usage, which never hit 50% (the highest I observed was 20%)