| T O P I C R E V I E W |
| BruteForce |
Posted - Aug 01 2008 : 08:06:18 AM
I am not sure whether VA does this trick, but I have noticed more than once the past days.
Take the following overly simplified example:
bool CFireiXCamera::IsFrameRateSupported
(
FIREi_PIXEL_FORMAT a_FireiPixelFormat,
FIREi_RES a_FireiResolution,
FIREi_FPS a_FrameRate
)
{
return m_pImpl->IsFrameRateSupported(a_FireiPixelFormat,
a_FireiResolution,
a_FrameRate);
}
This one just forwards a function call to the abstract base class of the implementation object. Both IsFrameRateSupported functions have exactly the same signature.
When I have typed "return m_pImpl->IsFrameRateSupported(" and then press "a", Visual Assist could match the type of the expected parameter against the types of the available variable names that start from "a" and propose the correct one as the default.
However, VA will propose to me a_FrameRate for all 3 parameters.
Warm Regards,
Dimitris Staikos
Unibrain |
| 1 L A T E S T R E P L I E S (Newest First) |
| accord |
Posted - Aug 01 2008 : 5:51:02 PM
We are considering something similar:
case=7200 (suggest all function parameters in one go based on variables with matching names) |
|
|
