safeproppage.shtml
来自「mfc资源大全包含MFC编程各个方面的源码」· SHTML 代码 · 共 100 行
SHTML
100 行
<HTML><!-- Header information--><HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META NAME="Author" CONTENT="Guy Gascoigne - Piggford"> <TITLE>PropertySheet - Modifying property sheet templates on Win95</TITLE></HEAD><!-- Set background properties --><body background="../fancyhome/back.gif" bgcolor="#FFFFFF" link="#B50029" vlink="#8E2323" alink="#FF0000" bgproperties="fixed"><!-- A word from our sponsors... --><table WIDTH="100%"><tr WIDTH="100%"><td><!--#exec cgi="/cgi/ads.cgi"--><td></tr></table><!-- Article Title --><CENTER><H3><FONT COLOR="#AOAO99">Modifying Property Sheet Templates on Win95</FONT></H3></CENTER><CENTER><H3><HR></H3></CENTER><!-- Author and contact details -->This article was contributed by <A HREF="mailto:Petr.Novotny@antek.cz">Petr Novotny</A>.<!-- Sample image and source code/demo project --><P>Download the <A HREF="safeproppage.zip">source</A></p><!-- The article... --><p>This code is written to fix the bug in CPropertySheet::DoModal() or CPropertySheet::Create() as described in MSKB article ID: Q158552.<p><h4>The description of the bug:</h4><p> (This bug is present for comctl32.dll version <4.70 and Windows95.)When a property sheet displays its property pages, it has to modifytheir templates. It tries to write into the memory; that works underWin32s (because the resources are writable) and it works under WinNT(because BeginResourceUpdate exists) but it fails under Win95 andraises an Access Violation. If you are not working with exceptions(try/catch(...), __try/__except, _set_se_translator) everything's OK -the OS gets the exception, unlocks the resources (or copies them towritable memory). However, if you're trying to be a good programmerand you add some code to your app to catch OS exceptions you are in adeep trouble.<p> The suggested fix #1 in the KB article (make the .rsrc sectionwritable) is OK but error-prone. It is not a very aestheticly pleasingsolution either.<p> The suggested fix #2 in the KB article is nonsense - or I didn'tunderstand correctly what it says.<p> The suggested fix #3 is unusable if you want to have__try/__except. Also, you can't catch access violations when theproperty sheet is active.<p> In this article, I offer another solution: I created aCSafePropertyPage class based on CPropertyPage. The one and onlydifference is that this modified property page uses a (potentiallywritable) copy of a dialog template instead of just using resourceID. It uses undocumented MFC class CDialogTemplate (defined inafxpriv.h) but you may look up the source code of CDialogTemplate andsupply your own CDialogTemplate::Load if you desperately want to keepthe documented/undocumented paradigm of MFC.<p> Attached are the source files - just include the header where youneed it and use CSafePropertyPage anywhere you'd use CPropertyPage.<!-- Remember to update this --><p>Last updated: 30 June 1998<P><HR><!-- Codeguru contact details --><TABLE BORDER=0 WIDTH="100%"><TR><TD WIDTH="33%"><FONT SIZE=-1><A HREF="http://www.codeguru.com">Goto HomePage</A></FONT></TD><TD WIDTH="33%"><CENTER><FONT SIZE=-2>© 1998 Zafir Anjum</FONT> </CENTER></TD><TD WIDTH="34%"><DIV ALIGN=right><FONT SIZE=-1>Contact me: <A HREF="mailto:zafir@home.com">zafir@home.com</A> </FONT></DIV></TD></TR></TABLE></BODY></HTML>⌨️ 快捷键说明
复制代码Ctrl + C
搜索代码Ctrl + F
全屏模式F11
增大字号Ctrl + =
减小字号Ctrl + -
显示快捷键?