This is a very annoying bug that's new since 1632 and makes VA X pretty much unusable for my current project.
Situation:
main.h:
struct AData
{
int foo, bar;
};
struct BData
{
int baz;
};
File1.cpp:
#include "main.h"
void Test()
{
AData data;
data.foo = 120;
}
File2.cpp:
#include "main.h"
void Test()
{
BData data;
data.baz = 34;
}
And now the annoying part:
Yes, because the function in File2.cpp is named equally as the function in File1.cpp, it thinks that 'data' is the same variable as in File1.cpp, and therefore of the type 'AData' instead of 'BData'. The navigation bar does it correctly, however.
Also, this only works for equally named functions in seperate files. If you put them in the same file, it works as expected.
This is a showstopper for me because I'm working on the PS3, and every SPU job is essentially it's own program with it's own main() function. And since I use similar variablenames for similar jobs, this is confusing the hell out of VA X.
I think I'm going back to 1626 until this is resolved (granted, it's a bit of my own fault as well as I shouldn't use the beta for production work 
).
