Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
 All Forums
 Visual Assist
 Technical Support
 String literals prepended with L don't display

You must be registered to post a reply.
Click here to register.

Format Mode:
Format: BoldItalicizeUnderlineStrikethrough Align LeftCenterAlign Right Insert Horizontal RuleInsert HyperlinkInsert E-mail AddressInsert Image Hosted on an External Site Insert CodeInsert Quoted TextInsert List

Forum code is on.
Html is off.
Smile [:)] Big Smile [:D] Cool [8D] Blush [:I]
Tongue [:P] Evil [):] Wink [;)] Clown [:o)]
Black Eye [B)] Eight Ball [8] Frown [:(] Shy [8)]
Shocked [:0] Angry [:(!] Dead [xx(] Sleepy [|)]
Kisses [:X] Approve [^] Disapprove [V] Question [?]

  Click to upload and insert an image.

Check to subscribe to this topic.

T O P I C    R E V I E W
kayako Posted - Apr 14 2006 : 2:57:23 PM
When the caret is placed over a symbol that is either a #define or const string and the string is prepended with L, the string does not appear in its entirety in the context definition window:

static const wchar_t *FOO = L"bar"; appears as "static const wchar_t *FOO = L"

VA_X.dll file version 10.2.1444.0 built 2006.03.12
VAOpsWin.dll version
VATE.dll version
DevEnv.exe version 8.0.50727.42
msenv.dll version 8.0.50727.42
Font: Courier New 13(Pixels)
Comctl32.dll version 6.0.2900.2180
WindowsNT 5.1 Build 2600 Service Pack 2
2 processors

11   L A T E S T    R E P L I E S    (Newest First)
support Posted - Nov 12 2010 : 3:32:30 PM
case=1131 is fixed in build 1836
feline Posted - Jul 07 2009 : 1:23:33 PM
I am seeing the same effect here. Thank you for the clear description.


This is a font specific problem, as you have already noticed. The fact that this font is "hacked" to show italic text when we are expecting bold text is probably part of the problem. For now the work around is to use a different font, or to stop using the hacked form that makes bold text italic.
ZyZyX Posted - Jul 07 2009 : 04:14:07 AM
VA_X.dll file version 10.5.1727.0 built 2009.06.12
Licensed to:
VA X: *** (11-user license) Support ends 2009.09.26
VA.NET 7.1: ***
DevEnv.exe version 8.0.50727.762
msenv.dll version 8.0.50727.762
Font: Envy Code R VS 13(Pixels)
Comctl32.dll version 6.0.2900.5512
Windows XP 5.1 Build 2600 S
2 processors (x86)

Platform: Win32
Stable Includes:
C:\\Program Files\\Microsoft Visual Studio 8\\VC\\include;
C:\\Program Files\\Microsoft Visual Studio 8\\VC\\atlmfc\\include;
C:\\Program Files\\Microsoft Visual Studio 8\\VC\\PlatformSDK\\include;
C:\\Program Files\\Microsoft Visual Studio 8\\SDK\\v2.0\\include;

Other Includes:

Stable Source Directories:
C:\\Program Files\\Microsoft Visual Studio 8\\VC\\atlmfc\\src\\mfc;
C:\\Program Files\\Microsoft Visual Studio 8\\VC\\atlmfc\\src\\mfcm;
C:\\Program Files\\Microsoft Visual Studio 8\\VC\\atlmfc\\src\\atl;
C:\\Program Files\\Microsoft Visual Studio 8\\VC\\crt\\src;

I've played a little with the fonts, and if I change the font for the strings it works fine. I have taken the fonts from the Humane color scheme:
Also, the string must have the font as Bold (actually the font is Italic), to reproduce it.
feline Posted - Jul 06 2009 : 1:32:49 PM
Can you please go to:

VA Options -> System Info -> Copy Info

and paste the details (from the clipboard) into your reply. This will give us the basic information about your setup.

I suspect this is related to the font you are using in the IDE. I notice you have text in italics, normally you cannot get the IDE to show you literal strings in italics.
ZyZyX Posted - Jul 06 2009 : 06:02:18 AM
The problem I have, it's inside the editor:

If I disable VA, the text is displayed properly:

This also happens on build 1724.
feline Posted - Jul 03 2009 : 4:59:50 PM
Are you seeing this inside the editor its self, or in a tooltip or in VA's context or definition fields?

The bug in case=1131 is that the literal string is simply not shown in tooltips and the definition field. You don't see the string displayed incorrectly.
ZyZyX Posted - Jul 03 2009 : 06:01:15 AM
I think I have a similar problem in 1727 :
When I try to write the following in C:
, I see:
where n can be any letter.
feline Posted - Jun 25 2009 : 12:18:44 PM
Unfortunately this is still a known bug, on our list of things to fix. I have increased the priority on this a bit for you.
SvenC Posted - Jun 25 2009 : 02:18:47 AM
Yes, I can confirm that as well with 1727, e.g.:

const TCHAR* something = _T("hello");

shows as

const TCHAR* something = _T()
owen.g Posted - Jun 24 2009 : 10:24:44 PM
I experience this behaviour regardless of the L. For instance, if I have

static const wchar_t* FOO = "bar";

It shows in the window as

static const wchar_t* FOO =

In fact it happens for any string literals, it seems, even multiple ones. So

RWCString guiPrefix = isOne() ? "one" : "two";

shows as

RWCString text = isOne() ? :

Semicolons are omitted too and I don't see the benefit of that.

Any update on whether and when this will be fixed? This is a pretty old report and I'm not sure what to do with the case number quoted.

I'm using build 1649.

rhummer Posted - Apr 14 2006 : 3:08:22 PM

© 2016 Whole Tomato Software, Inc Go To Top Of Page
Snitz Forums 2000