All Forums  Visual Assist  Feature Requests  Type-aware proposing of names for completion

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

Screensize: 640 x 480 800 x 600 1024 x 768 1280 x 1024 UserName: Password: Format: Font Andale Mono Arial Arial Black Book Antiqua Century Gothic Comic Sans MS Courier New Georgia Impact Lucida Console Script MT Bold Stencil Tahoma Times New Roman Trebuchet MS Verdana   Size 1 2 3 4 5 6   Color Black Blue Brown Green Red Violet Yellow Message: Forum code is on. Html is off. [quote][i]Originally posted by BruteForce[/i] [br]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 [/quote]   Check to include your profile signature. Check to subscribe to this topic.