| T O P I C R E V I E W |
| thx4alice |
Posted - Dec 29 2007 : 10:47:07 AM
1. BUILD 1561
2. BUILD 1624 (LATEST)
VA_X.dll file version 10.4.1624.0 built 2007.12.07
MSDev.exe version 6.0.9782.1
Devshl.dll version 6.0.9782.0
Devedit.pkg version 6.0.9782.0
Comctl32.dll version 5.82.2900.2982
Windows XP 5.1 Build 2600 Service Pack 2
2 processors
Platform: Win32 (x86)
Stable Includes:
C:\\Program Files\\Microsoft Visual Studio\\VC98\\INCLUDE;
C:\\Program Files\\Microsoft Visual Studio\\VC98\\MFC\\INCLUDE;
C:\\Program Files\\Microsoft Visual Studio\\VC98\\ATL\\INCLUDE;
Other Includes:
Stable Source Directories:
C:\\Program Files\\Microsoft Visual Studio\\VC98\\MFC\\SRC;
C:\\Program Files\\Microsoft Visual Studio\\VC98\\MFC\\INCLUDE;
C:\\Program Files\\Microsoft Visual Studio\\VC98\\ATL\\INCLUDE;
C:\\Program Files\\Microsoft Visual Studio\\VC98\\CRT\\SRC;
----------
sorry for poor English, :-)
using build 1561, there are no "mistyped errors" in codes
but using 1624, underlines(mistyped symbols) appeared everywhere
and VA-X's listbox doesn't work with members in underline
so now I'm using build 1561,
expecting next version to fix this weired bug
bye :-)
WinXP + VC++ 6.0 |
| 5 L A T E S T R E P L I E S (Newest First) |
| thx4alice |
Posted - Jan 03 2008 : 11:39:57 AM
quote:
Originally posted by feline
We have disabled underlining of mistyped symbols in VA 1624 for C# while we try to fix the problems with it, it was giving unreliable results, so this is probably why you are not seeing any such underlining.
Does your windows user name contain Unicode / extended characters? This might be causing VA problems.
If so can you follow the steps in this FAQ to tell VA to store its database in a different directory, with all English letters, and see if this helps:
http://docs.wholetomato.com?W332
thank you :-)
My work folder contained some Unicode, it was the problem.
for your help and kindness, now my VA works perfectly good :)
thank you again :-) |
| feline |
Posted - Jan 02 2008 : 10:18:18 AM
We have disabled underlining of mistyped symbols in VA 1624 for C# while we try to fix the problems with it, it was giving unreliable results, so this is probably why you are not seeing any such underlining.
Does your windows user name contain Unicode / extended characters? This might be causing VA problems.
If so can you follow the steps in this FAQ to tell VA to store its database in a different directory, with all English letters, and see if this helps:
http://docs.wholetomato.com?W332 |
| thx4alice |
Posted - Dec 29 2007 : 1:49:59 PM
plus.
I confirmed VISTA + VS2005 + VA1624 have same problem
I wonder VA1624 under KoreanWindows is causing this problem
but VA1624 under VS2005 C#, VB works fine with my environment,
only the C++ goes wrong way |
| thx4alice |
Posted - Dec 29 2007 : 1:16:58 PM
quote:
Originally posted by feline
Are you able to reproduce this problem in a new default project?
Does this only go wrong in certain files?
I am not seeing any problems with VC6 and VA 1624.
Unless we can find what is causing the problem, it is going to be hard to fix.
It's a default VC6 MFC project,
and I confirmed all of CPP files have same problem.
function's arguements are all underlined as mistyped symbols "~~~~"
- VC6's "Hello, World" console project
I tried something to find what is causing this problem...
using VA 1624 + VC6, if I type ';' in codes,
all the mistyped symbols are totally cleared,
and the VA's intellisense works fine...
but after seconds,
underlines of mistyped symbols are appeared again.
look at the below screen-shots
1. typing ';', mistyped symbols are totally cleared
2. after seconds, they are appeared again :-0
I don't know why.....
VA 1561 works fine with these codes (VC6 default MFC project)
I deleted VA, VC6 and re-installed VC6, VA,
but the problem is still exist
p.s : I'm not using any other plug-ins in vc6 except VA
sorry for my poor english :-)
(WinXP + VC6 + SP6)
|
| feline |
Posted - Dec 29 2007 : 12:46:52 PM
Are you able to reproduce this problem in a new default project?
Does this only go wrong in certain files?
I am not seeing any problems with VC6 and VA 1624.
Unless we can find what is causing the problem, it is going to be hard to fix. |
|
|
