ClassWizard VirtualFilter Options

I came across a problem with the VC++ ClassWizard a while ago. If you have a class derived from a standard MFC class, ClassWizard will offer to insert handlers for virtual function overrides. For example, for a class derived from CPropertyPage, you can add handlers for OnWizardNext, OnWizardFinish and so on. However, if you derive again, e.g.
CPropertyPage
CWizardPage
CWizPage1

Then ClassWizard will show virtual functions for CWizardPage but not for CWizPage1.

I discovered that this can be fixed by editing the ClassWizard *.CLW file and adding the 'VirtualFilter' option to the appropriate section. For example:

[CLS:WizPage1]
Type=0
BaseClass=WizardPage
HeaderFile=WizPage1.h
ImplementationFile=WizPage1.cpp
Filter=N
LastObject=WizPage1
VirtualFilter=idWC

The right hand side of VirtualFilter is a list of case-sensitive letters specifying which sets of virtual functions will be listed by ClassWizard. So, in the above example, ClassWizard will list virtual functions from CPropertyPage, CDialog, CWnd and CCmdTarget.

Here's the full list:

a CDatabase
b CListBox
c CComboBox
d CDialog
e -
f CFrameWnd
g COleMessageFilter
h CDialog
i CPropertyPage
j -
k CHttpServer
l COleClientItem
m -
n CHttpFilter
o OLE stuff
p CSplitterWnd
q CAsyncSocket
r CRecordSet
s COleDropSource
t COleDopTarget
u COleMessageFilter
v COleServerDoc
w COleControl
x CRecordset
y CAsyncMonikerFile
z -

A CWinApp
B Button? (DrawItem)
C CObject/CCmdTarget
D CDocument
E CEditView
F -
G -
H -
I CDocItem
J -
K -
L COleLinkingDoc
M CMDIFrameWnd
N -
O COleDocument
P COleIPFrameWnd
Q -
R CRecordView
S -
T CWinThread
U -
V CView
W CWnd
X -
Y -
Z -



Comments

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Today's agile organizations pose operations teams with a tremendous challenge: to deploy new releases to production immediately after development and testing is completed. To ensure that applications are deployed successfully, an automatic and transparent process is required. We refer to this process as Zero Touch Deployment™. This white paper reviews two approaches to Zero Touch Deployment--a script-based solution and a release automation platform. The article discusses how each can solve the key …

  • On-demand Event Event Date: October 29, 2014 It's well understood how critical version control is for code. However, its importance to DevOps isn't always recognized. The 2014 DevOps Survey of Practice shows that one of the key predictors of DevOps success is putting all production environment artifacts into version control. In this webcast, Gene Kim discusses these survey findings and shares woeful tales of artifact management gone wrong! Gene also shares examples of how high-performing DevOps …

Most Popular Programming Stories

More for Developers

RSS Feeds