Script updates, FAQ updates from web site
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@29772 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
@@ -46,6 +46,8 @@ See also <a href="faq.htm">top-level FAQ page</a>.
|
||||
<li><a href="#access">Is MS Active Accessibility supported?</a></li>
|
||||
<li><a href="#dspfmt">Why does Visual C++ complain about corrupted project files??</a></li>
|
||||
<li><a href="#crtmismatch">Visual C++ gives errors about multiply defined symbols, what can I do?</a></li>
|
||||
<li><a href="#directx">Why do I get compilation erros when using wxWidgets with DirectShow?</a></li>
|
||||
<li><a href="#handlewm">How do I handle Windows messages in my wxWidgets program?</a></li>
|
||||
</ul>
|
||||
<hr>
|
||||
|
||||
@@ -224,7 +226,7 @@ you need to configure wxWidgets to compile without debugging information: see
|
||||
docs/msw/install.txt for details. You may find that using configure instead
|
||||
of makefile.g95 is easier, particularly since you can maintain debug and
|
||||
release versions of the library simultaneously, in different directories.
|
||||
Also, run 'strip' after linking to remove all traces of debug info.
|
||||
Also, run 'strip' after linking to remove all traces of debug info.
|
||||
<P>
|
||||
|
||||
<H3><a name="mfc">Is wxWidgets compatible with MFC?</a></H3>
|
||||
@@ -335,7 +337,7 @@ example) and regenerate the makefile using tmake.<P>
|
||||
|
||||
tmake can be found at
|
||||
<a href="http://www.troll.no/freebies/tmake.html" target=_new>www.troll.no/freebies/tmake.html</a>.
|
||||
It's a Perl5 program and so it needs Perl (doh). There is a binary for
|
||||
It's a Perl5 program and so it needs Perl (doh). There is a binary for
|
||||
Windows (available from the same page), but I haven't used it, so
|
||||
I don't know if it works as flawlessly as "perl tmake" does (note
|
||||
for people knowing Perl: don't try to run tmake with -w, it won't
|
||||
@@ -344,7 +346,7 @@ just go to distrib/msw/tmake and type<P>
|
||||
|
||||
<pre>tmake -t b32 wxwin.pro -o ../../src/msw/makefile.b32</pre><P>
|
||||
|
||||
The makefiles are untested - I don't have any of Borland, Watcom or
|
||||
The makefiles are untested - I don't have any of Borland, Watcom or
|
||||
Symantec and I don't have enough diskspace to recompile even with
|
||||
VC6 using makefiles. The new makefiles are as close as possible to the
|
||||
old ones, but not closer: in fact, there has been many strange things
|
||||
@@ -451,7 +453,7 @@ First, you can use wxRegKey directly, for example:
|
||||
regKey.SetName(idName);
|
||||
|
||||
{
|
||||
wxLogNull dummy;
|
||||
wxLogNull dummy;
|
||||
if (!regKey.Create())
|
||||
{
|
||||
idName = wxT("HKEY_CURRENT_USER\\SOFTWARE\\My Company\\My Product\\Stuff\\");
|
||||
@@ -536,6 +538,33 @@ slightly smaller and faster.
|
||||
But the most important thing is to use the <strong>same</strong> CRT setting for
|
||||
all components of your project.
|
||||
|
||||
<h3><a name="#directx">Why do I get compilation erros when using wxWidgets with DirectShow?</a></h3>
|
||||
|
||||
If you get errors when including Microsoft DirectShow or DirectDraw headers,
|
||||
the following message from Peter Whaite could help:
|
||||
<blockquote>
|
||||
> This causes compilation errors within DirectShow:
|
||||
>
|
||||
> wxutil.h(125) : error C2065: 'EXECUTE_ASSERT' : undeclared identifier
|
||||
> amfilter.h(1099) : error C2065: 'ASSERT' : undeclared identifier
|
||||
|
||||
The reason for this is that __WXDEBUG__ is also used by the DXSDK (9.0
|
||||
in my case) to '#pragma once' the contents of
|
||||
DXSDK/Samples/C++/DirectShow/BaseClasses/wxdebug.h. So if __WXDEBUG__
|
||||
is defined, then wxdebug.h doesn't get included, and the assert macros
|
||||
don't get defined. You have to #undef __WXDEBUG__ before including the
|
||||
directshow baseclass's <streams.h>.
|
||||
</blockquote>
|
||||
|
||||
|
||||
<h3><a name="#handlewm">How do I handle Windows messages in my wxWidgets program?</a></h3>
|
||||
|
||||
To handle a Windows message you need to override a virtual
|
||||
<tt>MSWWindowProc()</tt> method in a wxWindow-derived class. You should then
|
||||
test if <tt>nMsg</tt> parameter is the message you need to process and perform
|
||||
the necessary action if it is or call the base class method otherwise.
|
||||
|
||||
|
||||
</font>
|
||||
|
||||
</BODY>
|
||||
|
Reference in New Issue
Block a user