Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
 All Forums
 Visual Assist
 Feature Requests
 Resolution of windows API defines

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

Screensize:
UserName:
Password:
Format: BoldItalicizeUnderlineStrikethrough Align leftCenterAlign right Insert horizontal ruleUpload and insert imageInsert hyperlinkInsert email addressInsert codeInsert quoted textInsert listInsert Emoji
   
Message:

Forum code is on.
Html is off.

 
Check to subscribe to this topic.
   

T O P I C    R E V I E W
Uniwares Posted - Nov 28 2006 : 7:37:05 PM
One thing that I always want and never get from VAX are the function definitions of the functions defined in the windows.h headers.
Most functions there are defined like

#ifdef UNICODE
#define ExpandEnvironmentStrings  ExpandEnvironmentStringsW
#else
#define ExpandEnvironmentStrings  ExpandEnvironmentStringsA
#endif // !UNICODE

So, clicking on a function shows only the define but not the underlying function definition. VAX could load this even from a predefined list (like the helper .h vax already uses for std lib and others).
Would be extremly helpful.
5   L A T E S T    R E P L I E S    (Newest First)
feline Posted - Dec 01 2006 : 08:35:33 AM
using VS2003 and VA 1541 ExpandEnvironmentStrings(); is working just fine for me. In fact the test project probably does not even have the correct include lines for this function call.

Is this function shown in italics for you, assuming you have this option turned on? Alt-g is taking me to the file:

C:\\Program Files\\Microsoft Visual Studio .NET 2003\\Vc7\\PlatformSDK\\include\\winbase.h

for reference, from this machines VA about:

Platform: Win32
Stable Includes:
C:\\WTL75\\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\\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:
Uniwares Posted - Nov 30 2006 : 7:12:24 PM
well typo on my part too, its VS2003
Anyway, alt+g beeps on me.
feline Posted - Nov 30 2006 : 08:31:06 AM
*oops* a typo on my part, I am also using 1541. I have just retested this in VS2005 professional, and it is working correctly for me.

If you try alt-g on ExpandEnvironmentStrings(); what happens? I am being offered:

winbase.h:5888
winbase.h:5886

as the two locations for the #define.
Uniwares Posted - Nov 29 2006 : 09:46:45 AM
vs2005, va 1541 - Not getting any tooltip for it, and the wizardbar shows the #define
feline Posted - Nov 29 2006 : 07:51:03 AM
What are you looking at? using VS2005 and VA 1540 if I call ExpandEnvironmentStrings() then I am getting the parameters tooltip, which lists two overloads, the A and W forms, and it is showing me the parameters for both.

Or are you looking at the VA wizard bar?

© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000