| T O P I C R E V I E W |
| Esone |
Posted - May 17 2006 : 03:56:55 AM
VA_X.dll file version 10.2.1445.0 built 2006.04.12
VAOpsWin.dll version 1.3.2.4
VATE.dll version 1.0.4.15
DevEnv.exe version 7.10.3077.0
msenv.dll version 7.10.3077.0
Font: Lerdana 13(Pixels)
Comctl32.dll version 5.81.4916.400
WindowsNT 5.0 Build 2195 Service Pack 4
Single processor
The problem:
VAX 1445 does NOT highlight matching () and {} inside the function body. What the VAX highlights fine is {} of the file-scope function/class body and () of function's formal parameters.
int main( /* highlights embracing () here */ )
{
// highlights embracing {} here
bool b = true;
if ( b /* does not highlight embracing () */ )
{
// does not highlight embracing {}
b = !b;
}
}
Same for any inner-scope () and {} - the outer-most braces are highlighted fine, whereas the inner - are NOT highlighted.
I run Windows 2000, and have both VS2003(Ent) and VS2005(Team) installed. I evaluated many older VAX versions and see that 1421 works fine in regard to highlighting matching (){}, but 1422-1445 do not highlight them, as described above. At the same time, VAX 1445 works fine on the neighbour PC, that runs WinXP.
BR,
Sergey Segin
PS. Feature request: how about highlighting matching <> for templates?
I know that comparison and shift operators may interfere here, but for most cases this would work good.
|
| 9 L A T E S T R E P L I E S (Newest First) |
| Esone |
Posted - Sep 05 2006 : 03:17:48 AM
Sounds beautiful!
I'm going to try it.
Thanks in advance! |
| support |
Posted - Aug 08 2006 : 01:24:59 AM
Case 1233 is fixed in build 1531. |
| feline |
Posted - Jul 16 2006 : 1:17:37 PM
no progress yet, sorry to report. i have upped the priority on this.
for now the best work around is to use a font that does not have this problem, although i am aware this is not an ideal answer. |
| Esone |
Posted - Jul 10 2006 : 03:58:51 AM
Dear support,
Have something changed in regard to this problem in latest VAX versions?
TIA, Sergey |
| feline |
Posted - Jun 01 2006 : 6:23:26 PM
sorry for the delay in getting back to you on this, i got side tracked. this is very odd, but i am definitely seeing the same thing here.
case=1233 |
| Esone |
Posted - Jun 01 2006 : 10:01:59 AM
Dear support,
How are you feeling about this bug? |
| Esone |
Posted - May 17 2006 : 1:30:22 PM
Another important clue. Try the following snippets with 2 fonts(any sizes): Verdana and Lucida Console.// indents by spaces
{
{
}
}
// indents by tabs
{
{
}
}
For spaces case both fonts work well. But for tabs case the verdana does not highlight inner {}. In other words, highlighting gets broken because of prepending TABs. Without prepending TABs, it works for any inner (){}. This may be a straight direction to the solution.
BTW, Verdana is not the only popular font problematic in this regard. Same problems apply for MS SansSerif, at least.
Looking forward for gurus' advices.
Sergey Segin |
| Esone |
Posted - May 17 2006 : 09:32:09 AM
quote:
Originally posted by support
Before we dig into this problem, does your selection of font make a difference? (You might first check to see what Text font your "neighbor PC" uses.)
Good point! When I set the font to "courier new", arial, georgia, tahoma - I have NO problems with this highlighting.
But when I choose verdana - the problem is here, as described above.
I do use custom-made verdana-based font, so I am eagerly looking for the solution for verdana. What is the specific verdana feature that prevents it from working correctly? Why verdana works fine for outer-scope {}, but not for inner-scope one? And why verdana worked fine for VAX up to 1421, but not for 1422+?
If that may help, I can send you my font.
Thank you very much!
Sergey Segin
|
| support |
Posted - May 17 2006 : 08:59:35 AM
Before we dig into this problem, does your selection of font make a difference? (You might first check to see what Text font your "neighbor PC" uses.) |
