Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
User name:
 Password:
Save Password
Forgot your password?

 All Forums
 Visual Assist
 Technical Support
 WTL class methods not correctly parsed		  New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

191919
New Member

3 Posts
Posted - May 28 2010 :  05:28:20 AM  Show Profile  Reply with Quote
In an ATL/WTL project (without MFC support), if I use a WTL class which

(1) is enabled by "using namespace WTL;"
(2) has an MFC homonymic sibling.

VA failed to recognized it as a WTL class (it is regarded as an MFC class).

WTL::CMenu::GetSubMenu returns a CMenu object, but MFC::CMenu::GetSubMenu returns a CMenu* object.

accord
Whole Tomato Software

United Kingdom
3287 Posts
Posted - May 28 2010 :  1:05:00 PM  Show Profile  Reply with Quote
We are planning to improve this at some point:

case=6948
Go to Top of Page

barto
Junior Member

Germany
19 Posts
Posted - Jun 13 2010 :  09:46:24 AM  Show Profile  Reply with Quote
I second the request. Is there an update already? The current behavior is driving me nuts.

My test-case is currently a member variable of type "CTabView", and when trying to get intellisense "m_tab." it lists all the members of MFC's CTabView and not WTL's...



VA_X.dll file version 10.6.1823.0 built 2010.05.06
Edited by - barto on Jun 13 2010 09:47:40 AM
Go to Top of Page

accord
Whole Tomato Software

United Kingdom
3287 Posts
Posted - Jun 14 2010 :  12:30:59 PM  Show Profile  Reply with Quote
I've added your vote to the case.
Go to Top of Page

drac
Senior Member

Germany
49 Posts
Posted - Jun 16 2010 :  05:09:50 AM  Show Profile  Reply with Quote
I second the request.

I've tried putting WTL include directory as first include in system
include directories, but VAX still picks up MFC headers.

VAX should at least respect the order of the system include headers.

One workaround is to use Visual C++'s intellisense (F12) to go to
the header file and hunt for the method.

Edit: removing $(VCInstallDir)atlmfc\\include made VAX to properly
recognize WTL headers, but then the project didn't compile anymore

Going further I've put back $(VCInstallDir)atlmfc\\include and removed
all "afx*" files from $(VCInstallDir)atlmfc\\include. This fixed VAX
WTL intellisense problem, and the WTL project compiled successfully
afterwards.

Please fix this, I don't think removing MFC is a workaround one can
suggest to customers.
Edited by - drac on Jun 16 2010 05:22:55 AM
Go to Top of Page

accord
Whole Tomato Software

United Kingdom
3287 Posts
Posted - Jun 16 2010 :  2:05:23 PM  Show Profile  Reply with Quote
Tricky
I have added your thoughts to the case.
For now, I can offer a little better workaround: if you go

VA Options -> Projects -> C/C++ Directories

and switch the platform to custom you will be able to remove the ...atlmfc\\include dir without affecting the compiler.
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000