| T O P I C R E V I E W |
| BruteForce |
Posted - Dec 04 2006 : 4:04:45 PM
Enter the following code into Visual Studio (I used 2005):
//------------------------------------------------------------------------------------
#ifdef FIREAPI_DLL_BUILD
#define FIREAPI_DLL_SPEC __declspec(dllexport)
#else
#define FIREAPI_DLL_SPEC __declspec(dllimport)
#endif
#define FIREAPI(type) FIREAPI_DLL_SPEC type WINAPI
FIREAPI(ULONG) C1394GetMaxSpeedToNode
(
IN HANDLE C1394AdapterHandle,
IN ULONG DestinationNodeID
);
int _tmain(int argc, _TCHAR* argv[])
{
ULONG x = C1394GetMaxSpeedToNode
return 0;
}
//------------------------------------------------------------------------------------
Now move to the end of the "ULONG x = " line and type a left parenthesis as if you are trying to complete the function call. You will see some incorrect behavior.
We use this macro for all the functions that our SDK provides to clients, so we would appreciate a timely fix.
Warm Regards,
Dimitris Staikos
Unibrain |
| 4 L A T E S T R E P L I E S (Newest First) |
| support |
Posted - Sep 13 2008 : 01:12:10 AM
case=3727 is fixed in build 1649 |
| feline |
Posted - Dec 05 2006 : 09:19:01 AM
case=3727 |
| BruteForce |
Posted - Dec 05 2006 : 08:06:24 AM
Yes, VA gets "trapped" into FIREAPI(ULONG) even as I type the second parameter to this function. This gets a little annoying on functions with 5-8 parameters, especially if you are used to always seeing the tooltip for each parameter as you type in the actual argument.
Thanks! |
| feline |
Posted - Dec 05 2006 : 07:52:32 AM
Placing this code into a test project, using VS2003 and VA 1541 I am seeing:
VA has highlighted the wrong part of the tooltip. Is this the problem you are seeing? Or are you seeing something else? |
