| Author |
 Topic  |
|
|
Heejin
New Member
4 Posts |
 Posted - Nov 16 2004 : 9:37:03 PM
|
1.
VA_X.dll file version 10.1.1287.0
Licensed to:
VA X:
VA.NET 7.1: xxxxx@xxxxx
VAOpsWin.dll version 1.2.0.4
DevEnv.exe version 7.10.3077.0
msenv.dll version 7.10.3077.0
Font: Fixedsys 13(Pixels)
Comctl32.dll version 5.82.2900.2180
2. Microsoft Visual C++ .NET
Microsoft Development Environment 2003 version 7.1.3088
(English)
3.
My visual assist X's coloring doesn't work at all!
If I scroll down, I can see some words that is painted in colors.
But soon it is uncolored again.
My option for Enhanced Syntax Coloring is set, of course.
I tried reinstalling va x for more than 10 times.
Also tried reinstall even VS.NET. =)
I just reinstalled va x newly release version.
IN VAIN...
Please help me on this...
Some special things I noticed.
1. Coloring works in Visual Assist.Net 7.1~ But not in X.
2. Font settings in VS.NET and VA X are different in size.
ex. VS.NET 8 -> VA X 11 : If I set IDE FontSys size 8, I see FontSys size 11 in VA X About dialog.
ex. VS.NET 7 -> VA X 9
ex. VS.NET 10 -> VA X 15
3. VA View sometimes turn to gray and never recover.
Specially when I put other view (like class view) into the box where VA View is, VA view is grayed and disabled. Furthermore
when I restart .NET IDE, right side of ide has black area of unknown and unrecoverable. I can't erase black area until I uninstall VA X and run .NET IDE without VA X and reinstall.
So I just don't uses VA View. =)
I am using window xp professional SP2 KOREAN, but it shouldn't be a problem.
You can tell how much effort I put on this. I read almost all the article here hoping it can help me, but none could. But I think I can put up with this problems if I just can use coloring. PLEASE HELP! |
Edited by - Heejin on Nov 16 2004 9:37:59 PM |
|
|
support
Whole Tomato Software
5566 Posts |
Posted - Nov 16 2004 : 11:31:44 PM
|
Font setting in the IDE options is in points; font is in pixels in the VA X options.
Can you try "Use defaults" in Tools|Options|Environment|Fonts and colors? |
 |
|
|
Heejin
New Member
4 Posts |
Posted - Nov 17 2004 : 01:28:33 AM
|
Surely, I did.
=)
|
|
|
|
Heejin
New Member
4 Posts |
Posted - Nov 18 2004 : 8:39:24 PM
|
Support, please reply.. |
|
|
|
AgedBOY
New Member
6 Posts |
Posted - Nov 19 2004 : 01:04:29 AM
|
So does my copy.
On most occasion, syntax coloring dose not work at all.
On rare occasion, it works, but it colors the symbols by any colors it likes.
It has got a new ability to color a group of characters of one symbol by one color, while, by other color for other characters. I just get a colorful source code view in this colorful autumn season.
Mine :
Microsoft Development Environment 2002, Chinese, version 7.0.9486.
VA_X.dll file version 10.1.1287.0
Licensed to:
VA X:
VA.NET 7.1:
VAOpsWin.dll version 1.2.0.4
DevEnv.exe version 7.0.9466.0
msenv.dll version 7.0.9466.0
Font: +?+?+?+?+?+? 12(Pixels)
Comctl32.dll version 5.82.2900.2180
WindowsNT 5.1 Build 2600 Service Pack 2
Single processor
XP SP2 |
Edited by - AgedBOY on Nov 19 2004 05:23:23 AM |
|
|
|
AgedBOY
New Member
6 Posts |
Posted - Nov 19 2004 : 01:29:46 AM
|
Here is a tiny example occured in one of my source code:
#ifndef VMREG_H
#define VMREG_H
...... |
|
|
|
LarryLeonard
Tomato Guru
USA
1041 Posts |
Posted - Nov 19 2004 : 09:17:29 AM
|
AgedBOY's example is like what I'm seeing now... there's something magical about underscores... coloring seems to stop or start on them...
|
|
|
|
support
Whole Tomato Software
5566 Posts |
Posted - Nov 19 2004 : 12:09:13 PM
|
We are investigating the problem. Unfortunately, we cannot reproduce it, at least not yet. We suspect multi-byte might be a culprit.
AgedBOY: Can you check the value of "Identifier" in the IDE options? Read this thread for details:
http://forum.wholetomato.com/forum/topic.asp?TOPIC_ID=1849 |
|
|
|
AgedBOY
New Member
6 Posts |
Posted - Nov 23 2004 : 03:20:30 AM
|
The value of "Identifier" in my IDE options is "Automatic". Both of my WinXP and VS.NET are Chinses version.
Hehe :-)
I see. You have not deal with this problem yet. Never mind, I like VA very much any way!
I'll wait for your new version patiently, and pay for my copy while this problem is solved. |
|
|
|
Newton
New Member
Brazil
2 Posts |
Posted - Nov 25 2004 : 08:50:15 AM
|
I have the same problem:
I use VS.NET 2003 (english version ) on WINXP (Protuguese Brazil version).
I changed Identifier value to "Use Defaults"(Automatic) but when i return to see this value it-?s turn to Custom.
I use VA since VA 4.X so i don-?t survive wihtout it.
Please, fix up this problem.
Cheers! :) |
|
|
|
mstone
Starting Member
1 Posts |
Posted - Dec 02 2004 : 10:40:30 AM
|
I'm getting the same problem.
I'm using XP, Visual Studio 2003, and the latest VAX release. It was working fine before I upgraded this morning.
Coloring seems to start after 'm_'
Also, not coloring class names properly. |
|
|
|
LarryLeonard
Tomato Guru
USA
1041 Posts |
Posted - Dec 02 2004 : 11:18:45 AM
|
There's another thread on this same issue, but what has fixed this issue for me, on two different machines, is to uninstall VAX, remove or rename every trace of it from the Registry and from the disk, and then re-install VAX. (I searched the Registry for the word 'tomato'.) Please post to this thread if you try this and it works.
|
|
|
|
kkokkal
Starting Member
1 Posts |
Posted - Dec 04 2004 : 10:27:38 AM
|
I just get out of the coloring problem.
The main action is to change the value of 'Identifier' to automatic.
(was it custom? hmmm... vague memory.. )
I have two computers. For one computer, the above was sufficient.
However, the other computer didn't escape from the coloring problem yet.
I tried to investigate the registry.
I executed 'regedit' and searched the item related font and color of VS .NET.
HKCU/Software/Microsoft/VisualStudio/7.1/FontAndColor/{...}
I think {...} would be an arbitrary string.
Anyway, you will find the items about font and color.
You can set the value of Identifier as the below figure.
And the important thing is you should add or set the value of
the localized name of Identifier, '-++?-?-?+?+?' in Korean.
I think you will understand what I did if you see the below figure.
If the method do not work on your computer,
I have no idea to solve the problem.
I just pray for your success. :-)
http://cyimg5.cyworld.nate.com/common/file_down.asp?redirect=%2Fr15401%2F2004%2F12%2F3%2F38%2Fvassist%2Egif
----------------------------------------------------------------
Append.
I had the coloring problem again after installing the new version 1289. So, I reinstalled the early version (1287)...
And tried like this:
1. set the registry value like the figure. (in red box).
2. Set the value of 'Identifier' in VS.NET to 'automatic'
|
Edited by - kkokkal on Dec 05 2004 11:22:13 AM |
|
|
|
support
Whole Tomato Software
5566 Posts |
|
|
Patrice Peyrano
Starting Member
1 Posts |
Posted - Dec 06 2004 : 06:16:39 AM
|
| I had same problem with 1287 (XPSP1 French version). I have install version 1289 and the problem disappeared. What it was the problem? |
Pat. |
|
|
|
Heejin
New Member
4 Posts |
Posted - Dec 06 2004 : 8:44:30 PM
|
Nothing works for me..
I cleaned registry and disk.
I changed registry as the one above said.
I installed 1289...
but all in vain....
I get coloring in VA.NET, but not in VAX. Doesn't it give you guys,support and the ones who are debugging,a clue?
|
|
|
|
Newton
New Member
Brazil
2 Posts |
Posted - Dec 07 2004 : 2:56:36 PM
|
I-?m do the same tasks on the notebook with win 2000 professional English version. I have Vc++ 6.0 with SP 6 and VS.net 2003 Version 7.1.3088 and Microsoft .Net Framework 1.1 version 1.1.4322 SP1 all in English Version
On VC++6.0 VA perform perfectly, but on VS.NET 2003 don-?t take effect :(
Cheers :)
|
|
|
|
Marc Kamradt
Junior Member
10 Posts |
Posted - Dec 09 2004 : 10:53:49 AM
|
Argh... nothing works here. 
I just tried the new version 1289. Just as 1287 and 1286. No coloring in the editor but coloring in completion list boxes etc.
I do have a German version of VS.NET 2003 Pro and if I do look into the "fonts and colors" dialog I find the German version of identifier "Bezeichner" as well as the English version "Identifier". This sounds pretty strange to me.
I also tried to put a new string registry key in "HKEY_CURRENT_USER\\Software\\Whole Tomato\\VAnet" called "Identifier" with the value "Bezeichner" but that did not help either.
Is there anything I can try to get this working? I really like this piece of software but it is now absolutely crippled. The worst thing is that switching back to the last "stable" version (1246) does not get coloring back to work. 
Marc
|
|
|
|
WannabeeDeveloper
Tomato Guru
Germany
775 Posts |
Posted - Dec 10 2004 : 04:44:53 AM
|
Marc,
are you sure you enabled Syntax-Coloring in the Options? (Options -> Environment -> Fonts & Colors -> Apply coloring to...)
I'm using the German Visual Studio .NET 2003 and VAX for ages and never really had a Problem with syntax-coloring.
I never even cared about what "Identifier" means in German etc, cause it always worked perfect from scratch...
Also have a look at my posting here.
|
 |
|
|
|
subatomic
New Member
3 Posts |
Posted - Dec 15 2004 : 4:51:22 PM
|
I have the same problem. I have weird broken up coloring. Within one file, some things are colored VA style, some are the default .net coloring. Some words are both, usually separated by an _ underscore.
This is an English language version of windows xp pro...
So what's the fix? :)
VA_X.dll file version 10.1.1287.0
Licensed to:
VA X: (license info removed by me...)
VA.NET 7.1:
VAOpsWin.dll version 1.2.0.4
DevEnv.exe version 7.10.3077.0
msenv.dll version 1.0.5849.1
Font: Courier New 13(Pixels)
Comctl32.dll version 5.82.2900.2180
WindowsNT 5.1 Build 2600 Service Pack 2
Single processor
Platform: Custom
Stable Includes:
c:\\program files\\microsoft visual studio .net 2003\\vc7\\include;
c:\\program files\\microsoft visual studio .net 2003\\vc7\\atlmfc\\include;
c:\\program files\\microsoft visual studio .net 2003\\vc7\\PlatformSDK\\include\\prerelease;
c:\\program files\\microsoft visual studio .net 2003\\vc7\\PlatformSDK\\include;
c:\\program files\\microsoft visual studio .net 2003\\sdk\\v1.1\\include;
Library Includes:
c:\\program files\\microsoft visual studio .net 2003\\vc7\\atlmfc\\src\\mfc;
c:\\program files\\microsoft visual studio .net 2003\\vc7\\atlmfc\\src\\atl;
c:\\program files\\microsoft visual studio .net 2003\\vc7\\crt\\src;
Other Includes:
C:\\Develop\\Trauma\\Dev\\Src;
C:\\Develop\\Trauma\\Dev\\Havok\\sdk\\include;
C:\\Develop\\Trauma\\Dev\\ATLAS\\Src\\At;
|
|
|
|
subatomic
New Member
3 Posts |
Posted - Dec 15 2004 : 4:53:10 PM
|
oh yeah, and this broke right after I upgraded from VA.NET... Maybe we didn't remove it correctly? but surely VAX would clean up after the old version right?
|
|
|
|
support
Whole Tomato Software
5566 Posts |
Posted - Dec 15 2004 : 11:25:39 PM
|
You can install VA X over VA.NET so you retain your VA.NET preferences. Once done, you are free to uninstall VA.NET.
Another option is to remove VA.NET before installing VA X. You get our default options. |
|
|
|
subatomic
New Member
3 Posts |
Posted - Dec 17 2004 : 1:16:55 PM
|
I've fixed the problem...
uninstall VA.NET that I had from before.
reinstall VAX using the 1289 (I previously had 1287 of VAX).
Somthing about that fixed the problem.
I can't believe how awful that problem was. the software was unusable with regard to coloring and autocompletion - the two main reasons i use it. (the only other reason I use is for C++/H switching)... |
|
|
| |
Topic |
|
Topic Locked
