| Author |
 Topic  |
|
|
WannabeeDeveloper
Tomato Guru
Germany
775 Posts |
 Posted - Oct 23 2005 : 04:48:56 AM
|
I got some questions/issues with the parser in Build 1428...
When hovering over a WinInet-function, it shows this tooltip:
Not very helpful, if you ask me... but why does it show the full info, while I am entering the same function?
I'd want this info while hovering over the completely finished function. Or, better: I'd like to have the parser scan my code for #define'd UNICODE or _UNICODE and display the "right" Functions (like SendMessageA or SendMessageW) in the Tooltip...
Also, distinguishing between WIDE and ANSI Code should be improved:
- Why doesn't this tooltip show both versions, SendMessageA and SendMessageW, when it is able to do so while entering?
|
 |
Edited by - WannabeeDeveloper on Oct 23 2005 04:55:25 AM |
|
|
feline
Whole Tomato Software
United Kingdom
19020 Posts |
Posted - Oct 25 2005 : 5:15:11 PM
|
there is virtually no spare space at the front of the tooltip before the text starts. this is used to tell VA and IDE tooltips apart, since they have different amounts of white space. with VA disabled the tooltips i am managing to get in VS 2003 have virtually no white space, so i suspect you are seeing IDE tooltips here.
the middle tooltip is from VA, since the IDE version of this tooltip has arrows.
if i am right then unfortunately VA cannot do anything about this, since these are not its tooltips. support have said before that they have never found a way to suppress tooltips in VS 2003, so you get a mix of IDE and VA tooltips.
as for picking up the value of #define's this has been discussed before. it would open a massive can of worms, since you can be using different #define's in the IDE settings in release and debug mode.
before you tell me that UNICODE is different where i work we have a solution made up of with over 80 projects. some projects are compiled in UNICODE mode, and some are not, apparently at random 
i have no idea why, but i am sure we are not the only people with really messy projects. in this case VA would have to change its mind about UNICODE as i move from one file to another... |
zen is the art of being at one with the two'ness |
 |
|
|
kevinsikes
Tomato Guru
USA
271 Posts |
Posted - Mar 14 2006 : 12:24:27 AM
|
I see this behavior with VAX tooltips as well:
Isn't there a VAX configuration file where Win32 API calls are maintained as "special" symbols in the global namespace, such that the #define xxxW vs. xxxA is ignored and the correct parameter list is displayed instead?
VA_X.dll file version 10.2.1444.0 built 2006.03.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: Bitstream Vera Sans Mono 13(Pixels)
Comctl32.dll version 5.82.2900.2180
WindowsNT 5.1 Build 2600 Service Pack 2
2 processors
Platform: Win32
Stable Includes:
d:\\compiler\\sdkfeb03\\include;
d:\\compiler\\wmsdk\\wmfsdk9\\include;
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\\SDK\\v1.1\\include;
d:\\compiler\\qdesign;
d:\\compiler\\mp3;
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:
|
Kevin Sikes
Infotainment Platform Design Engineer
Ford Motor Company |
|
|
|
feline
Whole Tomato Software
United Kingdom
19020 Posts |
Posted - Mar 21 2006 : 5:27:46 PM
|
| i have asked support about this, since i am not actually sure what is supposed to be happening here. |
zen is the art of being at one with the two'ness |
|
|
|
kevinsikes
Tomato Guru
USA
271 Posts |
Posted - Apr 26 2006 : 4:48:04 PM
|
| Is there any new news on this? I'm on build 1445 and still getting the unhelpful #define xxxxA/#define xxxxW tooltip instead of the function signature in both VC6 and VS2003 (see previous post for a screen shot). |
Kevin Sikes
Infotainment Platform Design Engineer
Ford Motor Company |
|
|
|
support
Whole Tomato Software
5566 Posts |
Posted - May 04 2006 : 10:43:05 AM
|
The 13xx builds of VA X eliminate from view the A and W variants and you see only the "useful" version. The 14xx builds show you the actual implementations which aren't so useful. (The "useful" version doesn't really exist -- it's just for presentation.)
We must have broken our code which collapses A and W variants.
case=1184 |
|
|
|
support
Whole Tomato Software
5566 Posts |
Posted - Sep 13 2008 : 01:09:34 AM
|
| case=1184 is fixed in build 1649 |
|
|
| |
Topic |
|
VAX 1428: Parser and Tooltips
