when should NOT we call the base class's corresponding function?

王朝网络·other·作者佚名  2006-01-09
宽屏版  字体: |||超大  

20041206:

when should NOT we call the base class's corresponding function?

void CDropDownBotton::OnKeyDown(UINT nChar, UINT nRepCnt, UINT nFlags)

{

// TODO: Add your message handler code here and/or call default

if(nChar == VK_RETURN || nChar == VK_ESCAPE)

{

if (m_pOrigParent->IsDropDownDialogDown() )

m_pOrigParent->OnDropdownButton();

}

//CButton::OnKeyDown(nChar, nRepCnt, nFlags);

}

in the code snippet above, the base class's corresponding function CButton::OnKeyDown(nChar, nRepCnt, nFlags); is comment out.

The reason is that the CButton has already been destroyed before we call CButton::OnKeyDown.

Another way to fix this kind of bug is to call CWnd::PostMeassage() instead of calling method to destroy CButton.

 
 
 
免责声明:本文为网络用户发布,其观点仅代表作者个人观点,与本站无关,本站仅提供信息存储服务。文中陈述内容未经本站证实,其真实性、完整性、及时性本站不作任何保证或承诺,请读者仅作参考,并请自行核实相关内容。
© 2005- 王朝网络 版权所有